From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>
Subject: Re: [PATCH v1 0/5] mfd: lpc_sch: Intel Quark support
Date: Mon, 01 Sep 2014 14:40:13 +0300 [thread overview]
Message-ID: <1409571613.30155.57.camel@linux.intel.com> (raw)
In-Reply-To: <20140829110043.GJ24579@lee--X1>
On Fri, 2014-08-29 at 12:00 +0100, Lee Jones wrote:
> On Fri, 29 Aug 2014, Andy Shevchenko wrote:
>
> > On Fri, 2014-08-22 at 13:58 +0300, Andy Shevchenko wrote:
> > > This brings support of the LPC SCH device found on Intel Quark SoC. Patches
> > > were compile tested, and driver runs on actual hardware.
> > >
> > > Please, note that PCI ID will be used in future in the gpio-sch driver.
> >
> > Bjorn, could you Ack or comment patch 3/5?
> >
> > Lee, do you have any comments on the series?
>
> I have marked them as 'important' and will get round to them when I
> can. This week has been hectic. I will get round to it next week.
Thanks for your comments. I will fix everything we agreed about and send
v2. For now I'm waiting for Rebecca's comment regarding to squashing
patch 1/5 and 2/5.
>
> > > Andy Shevchenko (4):
> > > mfd: lpc_sch: reduce duplicate code
> > > mfd: lpc_sch: better code manageability with chipset info struct
> > > mfd: lpc_sch: Add support for Intel Quark X1000
> > > mfd: lpc_sch: remove FSF address
> > >
> > > Josef Ahmad (1):
> > > pci_ids: add support for Intel Quark ILB
> > >
> > > drivers/mfd/lpc_sch.c | 207 ++++++++++++++++++++++++++++--------------------
> > > include/linux/pci_ids.h | 1 +
> > > 2 files changed, 122 insertions(+), 86 deletions(-)
> > >
> >
> >
>
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
prev parent reply other threads:[~2014-09-01 11:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 10:58 Andy Shevchenko
2014-08-22 10:58 ` [PATCH v1 1/5] mfd: lpc_sch: reduce duplicate code Andy Shevchenko
2014-09-01 9:13 ` Lee Jones
2014-09-01 10:21 ` Andy Shevchenko
2014-09-01 11:38 ` Lee Jones
2014-09-01 11:48 ` Andy Shevchenko
2014-09-01 13:46 ` Lee Jones
2014-09-01 14:00 ` Andy Shevchenko
2014-08-22 10:58 ` [PATCH v1 2/5] mfd: lpc_sch: better code manageability with chipset info struct Andy Shevchenko
2014-09-01 9:16 ` Lee Jones
2014-09-01 10:25 ` Andy Shevchenko
2014-09-02 0:17 ` Chang, Rebecca Swee Fun
2014-09-02 7:25 ` Lee Jones
2014-08-22 10:58 ` [PATCH v1 3/5] pci_ids: add support for Intel Quark ILB Andy Shevchenko
2014-08-29 14:27 ` Bjorn Helgaas
2014-09-01 9:14 ` Andy Shevchenko
2014-09-02 0:14 ` Chang, Rebecca Swee Fun
2014-08-22 10:58 ` [PATCH v1 4/5] mfd: lpc_sch: Add support for Intel Quark X1000 Andy Shevchenko
2014-09-01 9:22 ` Lee Jones
2014-09-01 10:28 ` Andy Shevchenko
2014-09-01 11:31 ` Lee Jones
2014-08-22 10:58 ` [PATCH v1 5/5] mfd: lpc_sch: remove FSF address Andy Shevchenko
2014-08-29 14:26 ` Bjorn Helgaas
2014-08-29 9:57 ` [PATCH v1 0/5] mfd: lpc_sch: Intel Quark support Andy Shevchenko
2014-08-29 11:00 ` Lee Jones
2014-09-01 11:40 ` Andy Shevchenko [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=1409571613.30155.57.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rebecca.swee.fun.chang@intel.com \
--cc=sameo@linux.intel.com \
/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
Powered by JetHome