From: Guenter Roeck <linux@roeck-us.net>
To: Vicki Pfau <vi@endrift.com>,
linux-hwmon@vger.kernel.org, linux-pci@vger.kernel.org,
Brian Woods <brian.woods@amd.com>
Subject: Re: [PATCH 2/2] hwmon: (k10temp) Add PCI device IDs for family 17h, model 70h
Date: Sun, 14 Jul 2019 14:33:28 -0700 [thread overview]
Message-ID: <94313f9f-e37a-40f5-ddbe-ebc9e6b01539@roeck-us.net> (raw)
In-Reply-To: <20190714183209.29916-2-vi@endrift.com>
On 7/14/19 11:32 AM, Vicki Pfau wrote:
> Add PCI device IDs for the new AMD Ryzen 3xxx (Matisse) CPUs to k10temp,
> as they function identically from k10temp's point of view.
>
> Signed-off-by: Vicki Pfau <vi@endrift.com>
Acked-by: Guenter Roeck <linux@roeck-us.net>
I can not directly apply this patch since it depends on patch 1
of the series. You might want to resubmit and include x86 maintainers;
otherwise I don't see a path to get it accepted.
Guenter
> ---
> drivers/hwmon/k10temp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hwmon/k10temp.c b/drivers/hwmon/k10temp.c
> index c77e89239dcd..5c1dddde193c 100644
> --- a/drivers/hwmon/k10temp.c
> +++ b/drivers/hwmon/k10temp.c
> @@ -349,6 +349,7 @@ static const struct pci_device_id k10temp_id_table[] = {
> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_17H_DF_F3) },
> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_17H_M10H_DF_F3) },
> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_17H_M30H_DF_F3) },
> + { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_17H_M70H_DF_F3) },
> { PCI_VDEVICE(HYGON, PCI_DEVICE_ID_AMD_17H_DF_F3) },
> {}
> };
>
next prev parent reply other threads:[~2019-07-14 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 18:32 [PATCH 1/2] x86/amd_nb: Add PCI device IDs for family 17h, model 70h Vicki Pfau
2019-07-14 18:32 ` [PATCH 2/2] hwmon: (k10temp) " Vicki Pfau
2019-07-14 21:33 ` Guenter Roeck [this message]
2019-07-14 21:31 ` [PATCH 1/2] x86/amd_nb: " Guenter Roeck
2019-07-23 23:10 ` Bjorn Helgaas
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=94313f9f-e37a-40f5-ddbe-ebc9e6b01539@roeck-us.net \
--to=linux@roeck-us.net \
--cc=brian.woods@amd.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=vi@endrift.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).