From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andy Shevchenko <andy@infradead.org>,
Lee Jones <lee.jones@linaro.org>, Takashi Iwai <tiwai@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bin Gao <bin.gao@intel.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2] mfd: Add Cherrytrail WhiskeyCove PMIC driver
Date: Tue, 28 Feb 2017 14:23:38 +0100 [thread overview]
Message-ID: <aff1cc24-819e-0936-2e5f-cdfd452220f0@redhat.com> (raw)
In-Reply-To: <CAHp75Vecem11Fp58+u9dWkA4OJG0UzZakGxzy6YtNpawDsMkGg@mail.gmail.com>
Hi,
On 27-02-17 23:06, Andy Shevchenko wrote:
> On Mon, Feb 27, 2017 at 11:38 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Add mfd driver for Intel CHT WhiskeyCove PMIC, based on various non
>> upstreamed CHT WhiskeyCove PMIC patches. For now this just adds a minimal
>> version which implements just enough to get ACPI PMIC opregion support to
>> work, so that suspend/resume will work on machines with this PMIC.
>>
>> Cc: Bin Gao <bin.gao@intel.com>
>> Cc: Felipe Balbi <felipe.balbi@linux.intel.com>
>> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> Changes in v2:
>
> You were too fast. Please, give a time for reviewers to do their job.
>
> So, please address comments per v2 first.
>
>> -Since this uses plain mfd and not the intel_soc_pmic stuff give it
>> its own Kconfig and allow this to be built as a module
>
>> -Add missing #include <acpi/acpi_bus.h>
>
> Do we need it explicitly included?
I was trying to fix a kbuild bot error with this
(Takashi has it on a topic-branch), but it only made it
worse. so I'm dropping this again for v3, instead adding
"depends on ACPI" to the Kconfig for this, which will
hopefully really fix the kbuild bot errors.
Regards,
Hans
prev parent reply other threads:[~2017-02-28 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 21:38 Hans de Goede
2017-02-27 22:06 ` Andy Shevchenko
2017-02-28 13:23 ` Hans de Goede [this message]
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=aff1cc24-819e-0936-2e5f-cdfd452220f0@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=bin.gao@intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®