From: Lee Jones <lee.jones@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Ed Schaller <schallee@darkmist.net>, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] mfd: intel-lpss: Add Intel Lakefield PCH PCI IDs
Date: Tue, 23 Nov 2021 09:12:42 +0000 [thread overview]
Message-ID: <YZywikZuMSnbqpI1@google.com> (raw)
In-Reply-To: <YZvYhBB23ITS+Pw0@smile.fi.intel.com>
On Mon, 22 Nov 2021, Andy Shevchenko wrote:
> On Mon, Nov 22, 2021 at 04:36:06PM -0600, Ed Schaller wrote:
> > Add new IDs of the Intel Lakefield chip to the list of supported
> > devices.
>
> Thank you for the patch, it LGTM,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
>
> > Signed-off-by: Ed Schaller <schallee@darkmist.net>
> > ---
> > drivers/mfd/intel-lpss-pci.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/drivers/mfd/intel-lpss-pci.c b/drivers/mfd/intel-lpss-pci.c
> > index a872b4485eac..9700e5acd0cd 100644
> > --- a/drivers/mfd/intel-lpss-pci.c
> > +++ b/drivers/mfd/intel-lpss-pci.c
> > @@ -359,7 +359,14 @@ static const struct pci_device_id intel_lpss_pci_ids[] = {
> > /* LKF */
> > { PCI_VDEVICE(INTEL, 0x98a8), (kernel_ulong_t)&bxt_uart_info },
> > { PCI_VDEVICE(INTEL, 0x98a9), (kernel_ulong_t)&bxt_uart_info },
> > + { PCI_VDEVICE(INTEL, 0x98aa), (kernel_ulong_t)&bxt_info },
> > + { PCI_VDEVICE(INTEL, 0x98c5), (kernel_ulong_t)&bxt_i2c_info },
> > + { PCI_VDEVICE(INTEL, 0x98c6), (kernel_ulong_t)&bxt_i2c_info },
> > { PCI_VDEVICE(INTEL, 0x98c7), (kernel_ulong_t)&bxt_uart_info },
> > + { PCI_VDEVICE(INTEL, 0x98e8), (kernel_ulong_t)&bxt_i2c_info },
> > + { PCI_VDEVICE(INTEL, 0x98e9), (kernel_ulong_t)&bxt_i2c_info },
> > + { PCI_VDEVICE(INTEL, 0x98ea), (kernel_ulong_t)&bxt_i2c_info },
> > + { PCI_VDEVICE(INTEL, 0x98eb), (kernel_ulong_t)&bxt_i2c_info },
> > /* SPT-LP */
> > { PCI_VDEVICE(INTEL, 0x9d27), (kernel_ulong_t)&spt_uart_info },
> > { PCI_VDEVICE(INTEL, 0x9d28), (kernel_ulong_t)&spt_uart_info },
Odd. This didn't make it into my inbox.
Would you mind gathering Andy's R-b and re-sending please Ed?
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-11-23 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 22:36 [PATCH] mfd: intel-lpss: Add Intel Lakefield PCH PCI IDs Ed Schaller
2021-11-22 17:51 ` Andy Shevchenko
2021-11-23 9:12 ` Lee Jones [this message]
2021-11-23 9:38 ` Andy Shevchenko
2021-11-23 10:12 ` Lee Jones
2021-11-23 10:22 ` Andy Shevchenko
[not found] ` <CAJo6XL_DfWcVbT92X8fsd=mvs9AkzNQ2A1hPJpeGxrqC3BuL=g@mail.gmail.com>
2021-11-23 14:04 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2021-11-23 18:01 Ed Schaller
2021-11-24 8:31 ` Lee Jones
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=YZywikZuMSnbqpI1@google.com \
--to=lee.jones@linaro.org \
--cc=andriy.shevchenko@intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=schallee@darkmist.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.