From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Zhang Rui <rui.zhang@intel.com>, edubezval@gmail.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] thermal: int340x: processor_thermal: Add Coffee Lake support
Date: Wed, 01 Nov 2017 09:38:42 -0700 [thread overview]
Message-ID: <1509554322.7135.9.camel@linux.intel.com> (raw)
In-Reply-To: <1509507215.3080.82.camel@intel.com>
On Wed, 2017-11-01 at 11:33 +0800, Zhang Rui wrote:
> On Thu, 2017-10-19 at 14:51 -0700, Srinivas Pandruvada wrote:
> > Add new PCI id for Coffee lake processor thermal device.
> >
> > Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel
> > .c
> > om>
> > ---
> > drivers/thermal/int340x_thermal/processor_thermal_device.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git
> > a/drivers/thermal/int340x_thermal/processor_thermal_device.c
> > b/drivers/thermal/int340x_thermal/processor_thermal_device.c
> > index e724a23..1d9f524 100644
> > --- a/drivers/thermal/int340x_thermal/processor_thermal_device.c
> > +++ b/drivers/thermal/int340x_thermal/processor_thermal_device.c
> > @@ -32,6 +32,7 @@
> >
> > /* CannonLake thermal reporting device */
> > #define PCI_DEVICE_ID_PROC_CNL_THERMAL 0x5a03
> > +#define PCI_DEVICE_ID_PROC_CFL_THERMAL 0x3E83
> >
>
> shouldn't it be added into proc_thermal_pci_ids[]?
Yes. Lost during rebase.
Thanks for finding. I am sending whole series again.
-Srinivas
next prev parent reply other threads:[~2017-11-01 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 21:51 [PATCH 0/3] thermal: Support for Coffee Lake and Cannon Lake Srinivas Pandruvada
2017-10-19 21:51 ` [PATCH 1/3] thermal: int340x: processor_thermal: Add Cannon Lake support Srinivas Pandruvada
2017-10-19 21:51 ` [PATCH 2/3] thermal: int340x: processor_thermal: Add Coffee " Srinivas Pandruvada
2017-11-01 3:33 ` Zhang Rui
2017-11-01 16:38 ` Srinivas Pandruvada [this message]
2017-10-19 21:51 ` [PATCH 3/3] thermal: pch: Add Cannon " Srinivas Pandruvada
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=1509554322.7135.9.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@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).