From: "Rafael J. Wysocki" <rafael@kernel.org>
To: "Kammela, Gayatri" <gayatri.kammela@intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Alex Hung <alex.hung@canonical.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@verdurent.com>,
"Prestopine, Charles D" <charles.d.prestopine@intel.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Zhang, Rui" <rui.zhang@intel.com>,
"Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
Subject: Re: [PATCH v3 0/5] drivers: Add Tiger Lake hardware IDs to support ACPI,
Date: Thu, 19 Dec 2019 22:55:43 +0100 [thread overview]
Message-ID: <CAJZ5v0ji2f7XsR2__t5Fw8Vi1hB2XXHbp-LCZABN29yQ4VOyKw@mail.gmail.com> (raw)
In-Reply-To: <MWHPR11MB1278E9E06FBB5847444B11F3F2510@MWHPR11MB1278.namprd11.prod.outlook.com>
On Mon, Dec 16, 2019 at 10:57 PM Kammela, Gayatri
<gayatri.kammela@intel.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Rafael J. Wysocki <rafael@kernel.org>
> > Sent: Monday, December 16, 2019 1:36 PM
> > To: Kammela, Gayatri <gayatri.kammela@intel.com>
> > Cc: Linux PM <linux-pm@vger.kernel.org>; Platform Driver <platform-driver-
> > x86@vger.kernel.org>; Alex Hung <alex.hung@canonical.com>; ACPI Devel
> > Maling List <linux-acpi@vger.kernel.org>; Len Brown <lenb@kernel.org>;
> > Rafael J. Wysocki <rjw@rjwysocki.net>; Linux Kernel Mailing List <linux-
> > kernel@vger.kernel.org>; Daniel Lezcano <daniel.lezcano@linaro.org>; Amit
> > Kucheria <amit.kucheria@verdurent.com>; Prestopine, Charles D
> > <charles.d.prestopine@intel.com>; Darren Hart <dvhart@infradead.org>;
> > Rafael J . Wysocki <rafael@kernel.org>; Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com>; Zhang, Rui <rui.zhang@intel.com>;
> > Pandruvada, Srinivas <srinivas.pandruvada@intel.com>
> > Subject: Re: [PATCH v3 0/5] drivers: Add Tiger Lake hardware IDs to support
> > ACPI,
> >
> > On Mon, Dec 16, 2019 at 7:33 PM Gayatri Kammela
> > <gayatri.kammela@intel.com> wrote:
> > >
> > > Hi,
> > >
> > > Tiger Lake supports devices whose hardware IDs are changed for various
> > > drivers. Hence, add the new hardware IDs.
> > >
> > > Patch 1: Add Tiger Lake support to DPTF driver Patch 2: Add Tiger Lake
> > > support to fan driver Patch 3: Add Tiger Lake support to device_pm
> > > Patch 4: Add Tiger Lake support to Intel's HID driver Patch 5: Add
> > > Tiger Lake support to thermal driver
> >
> > I'm going to apply the whole series (for 5.6) if nobody has any issues with
> > that.
> >
> > Thanks!
>
> Thank you Rafael!
So applying as 5.6 material with rewritten subjects and changelogs and
with patches [2/5] and [3/5] folded together.
Thanks!
next prev parent reply other threads:[~2019-12-19 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 18:31 [PATCH v3 0/5] drivers: Add Tiger Lake hardware IDs to support ACPI, Gayatri Kammela
2019-12-16 18:31 ` [PATCH v3 1/5] acpi: dptf: Add new Tiger Lake hardware IDs to support DPTF drivers in ACPI Gayatri Kammela
2019-12-16 18:31 ` [PATCH v3 2/5] acpi: fan: Add new Tiger Lake hardware ID to support fan driver " Gayatri Kammela
2019-12-16 18:31 ` [PATCH v3 3/5] acpi: device_pm: Add new Tiger Lake hardware ID to support ACPI device power management Gayatri Kammela
2019-12-16 18:31 ` [PATCH v3 4/5] platform/x86: intel-hid: Add new Tiger Lake hardware ID to support HID driver Gayatri Kammela
2019-12-16 18:31 ` [PATCH v3 5/5] thermal: int340x_thermal: Add new Tiger Lake hardware IDs to support thermal driver Gayatri Kammela
2019-12-17 1:37 ` Zhang Rui
2019-12-16 21:35 ` [PATCH v3 0/5] drivers: Add Tiger Lake hardware IDs to support ACPI, Rafael J. Wysocki
2019-12-16 21:56 ` Kammela, Gayatri
2019-12-19 21:55 ` Rafael J. Wysocki [this message]
2019-12-19 22:14 ` Kammela, Gayatri
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=CAJZ5v0ji2f7XsR2__t5Fw8Vi1hB2XXHbp-LCZABN29yQ4VOyKw@mail.gmail.com \
--to=rafael@kernel.org \
--cc=alex.hung@canonical.com \
--cc=amit.kucheria@verdurent.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=charles.d.prestopine@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=dvhart@infradead.org \
--cc=gayatri.kammela@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@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;
as well as URLs for NNTP newsgroup(s).