linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Brunner <Michael.Brunner@kontron.com>
To: "lee.jones@linaro.org" <lee.jones@linaro.org>
Cc: "linux@roeck-us.net" <linux@roeck-us.net>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>,
	"mibru@gmx.de" <mibru@gmx.de>,
	"vkrasnov@dev.rtsoft.ru" <vkrasnov@dev.rtsoft.ru>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mvanyulin@dev.rtsoft.ru" <mvanyulin@dev.rtsoft.ru>
Subject: Re: [PATCH v2] mfd: kempld-core: Check for DMI definition before ACPI
Date: Mon, 16 Nov 2020 06:46:19 +0000	[thread overview]
Message-ID: <0588a23d0fc7dbde4c969722ce7a9c476a93ec0a.camel@kontron.com> (raw)
In-Reply-To: <20201113101623.GG3718728@dell>

On Fri, 2020-11-13 at 10:16 +0000, Lee Jones wrote:
> On Tue, 10 Nov 2020, Michael Brunner wrote:
> 
> > Change the detection order to priorize DMI table entries over
> > available
> > ACPI entries.
> > 
> > This makes it more easy for product developers to patch product
> > specific
> > handling into the driver.
> > Furthermore it allows to simplify the implementation a bit and
> > especially to remove the need to force synchronous probing.
> > Based on the following commit introduced with v5.10-rc1:
> > commit e8299c7313af ("mfd: Add ACPI support to Kontron PLD driver")
> 
> This section should also be removed from the change log.

No problem, just sent v3.

Thanks,
  Michael

  reply	other threads:[~2020-11-16  6:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  7:46 [PATCH] mfd: kempld-core: Check for DMI definition before ACPI Michael Brunner
2020-11-10 14:39 ` Guenter Roeck
2020-11-10 15:41   ` Michael Brunner
2020-11-10 16:10     ` Guenter Roeck
2020-11-10 15:23 ` [PATCH v2] " Michael Brunner
2020-11-10 16:11   ` Guenter Roeck
2020-11-13 10:14     ` Lee Jones
2020-11-13 10:16   ` Lee Jones
2020-11-16  6:46     ` Michael Brunner [this message]
2020-11-16  6:42   ` [PATCH v3] " Michael Brunner
2020-11-27  7:53     ` Lee Jones
2020-11-30 13:08       ` Michael Brunner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0588a23d0fc7dbde4c969722ce7a9c476a93ec0a.camel@kontron.com \
    --to=michael.brunner@kontron.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mibru@gmx.de \
    --cc=mvanyulin@dev.rtsoft.ru \
    --cc=sameo@linux.intel.com \
    --cc=vkrasnov@dev.rtsoft.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).