From: Guenter Roeck <linux@roeck-us.net>
To: Marcel Bocu <marcel.p.bocu@gmail.com>
Cc: Vicki Pfau <vi@endrift.com>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, "Woods, Brian" <Brian.Woods@amd.com>,
Clemens Ladisch <clemens@ladisch.de>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2 2/2] hwmon/k10temp: Add support for AMD family 17h, model 70h CPUs
Date: Mon, 22 Jul 2019 11:23:34 -0700 [thread overview]
Message-ID: <20190722182333.GA16112@roeck-us.net> (raw)
In-Reply-To: <20190722174653.2391-1-marcel.p.bocu@gmail.com>
On Mon, Jul 22, 2019 at 08:46:53PM +0300, Marcel Bocu wrote:
> It would seem like model 70h is behaving in the same way as model 30h,
> so let's just add the new F3 PCI ID to the list of compatible devices.
>
> Unlike previous Ryzen/Threadripper, Ryzen gen 3 processors do not need
> temperature offsets anymore. This has been reported in the press and
> verified on my Ryzen 3700X by checking that the idle temperature
> reported by k10temp is matching the temperature reported by the
> firmware.
>
> Vicki Pfau sent an identical patch after I checked that no-one had
> written this patch. I would have been happy about dropping my patch but
> unlike for his patch series, I had already Cc:ed the x86 people and
> they already reviewed the changes. Since Vicki has not answered to
> any email after his initial series, let's assume he is on vacation
> and let's avoid duplication of reviews from the maintainers and merge
> my series. To acknowledge Vicki's anteriority, I added his S-o-b to
> the patch.
>
> v2, suggested by Guenter Roeck and Brian Woods:
> - rename from 71h to 70h
>
> Signed-off-by: Vicki Pfau <vi@endrift.com>
> Signed-off-by: Marcel Bocu <marcel.p.bocu@gmail.com>
> Tested-by: Marcel Bocu <marcel.p.bocu@gmail.com>
>
Applied to hwmon-next.
Note that I made a small change to the description of each patch:
s/ he / she /
s/his/her/
Guenter
next prev parent reply other threads:[~2019-07-22 18:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 18:26 [PATCH 1/2] x86/amd_nb: Add PCI device IDs for family 17h, model 71h Marcel Bocu
2019-07-18 18:26 ` [PATCH 2/2] hwmon/k10temp: Add support for AMD family 17h, model 71h CPUs Marcel Bocu
2019-07-22 17:46 ` [PATCH v2 2/2] hwmon/k10temp: Add support for AMD family 17h, model 70h CPUs Marcel Bocu
2019-07-22 18:23 ` Guenter Roeck [this message]
2019-07-22 21:12 ` Marcel Bocu
[not found] ` <20190718193330.GA23809@roeck-us.net>
2019-07-19 7:40 ` [PATCH 1/2] x86/amd_nb: Add PCI device IDs for family 17h, model 71h Marcel Bocu
2019-07-19 13:27 ` Guenter Roeck
2019-07-19 15:30 ` Marcel Bocu
2019-07-19 16:08 ` Guenter Roeck
2019-07-22 8:59 ` Thomas Gleixner
2019-07-22 9:12 ` Borislav Petkov
2019-07-22 16:04 ` Woods, Brian
2019-07-22 16:51 ` Guenter Roeck
2019-07-22 17:39 ` Woods, Brian
2019-07-22 18:04 ` Marcel Bocu
2019-07-22 18:11 ` Vicki Pfau
2019-07-22 21:09 ` Marcel Bocu
2019-07-22 22:01 ` Guenter Roeck
2019-07-22 17:45 ` [PATCH v2 1/2] x86/amd_nb: Add PCI device IDs for family 17h, model 70h Marcel Bocu
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=20190722182333.GA16112@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Brian.Woods@amd.com \
--cc=bp@alien8.de \
--cc=clemens@ladisch.de \
--cc=hpa@zytor.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=marcel.p.bocu@gmail.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vi@endrift.com \
--cc=x86@kernel.org \
/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).