From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-edac@vger.kernel.org, X86 ML <x86@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
bberg@redhat.com, bp@suse.de
Subject: Re: [PATCH 1/3] x86/mce/therm_throt: remove unused platform_thermal_notify function pointer
Date: Tue, 14 Apr 2020 07:49:15 -0700 [thread overview]
Message-ID: <64f368b6bfde0611d3a1bc24884242bc4fb4cecd.camel@linux.intel.com> (raw)
In-Reply-To: <CAHmME9rOzmF4K965U69tFZi2SS3rW9SHed2bJ=_PD+xu8LqMYw@mail.gmail.com>
On Mon, 2020-04-13 at 22:21 -0600, Jason A. Donenfeld wrote:
> On Mon, Apr 13, 2020 at 9:56 PM Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> > On Tue, 2020-04-07 at 00:33 -0600, Jason A. Donenfeld wrote:
> > > A long time ago platform_thermal_notify was added as some generic
> > > mechanism for platform drivers to hook thermal events. It seems
> > > as
> > > though this has been entirely superseded, and nothing uses it.
> > > Remove
> > > the plumbing for this, since this code runs in an interrupt hot
> > > path.
> > Good idea.
>
> Will you take this into your tree?
I am not the maintainer of this tree. So I don't decide this. I can
just give my opinion.
> If not, how do your thermal patches
> usually go in? A reviewed-by might be useful in that case.
For this patch:
Reviewed-by: Pandruvada, Srinivas <srinivas.pandruvada@linux.intel.com>
>
> Jason
prev parent reply other threads:[~2020-04-14 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 6:33 [PATCH 1/3] x86/mce/therm_throt: remove unused platform_thermal_notify function pointer Jason A. Donenfeld
2020-04-07 6:33 ` [PATCH 2/3] x86/mce/therm_throt: allow disabling verbose logging Jason A. Donenfeld
2020-04-07 6:33 ` [PATCH 3/3] x86/mce/therm_throt: allow disabling the thermal vector altogether Jason A. Donenfeld
2020-04-14 3:38 ` Srinivas Pandruvada
2020-04-14 4:21 ` Jason A. Donenfeld
2020-04-14 14:45 ` Srinivas Pandruvada
2020-04-14 19:41 ` Jason A. Donenfeld
2020-04-14 19:58 ` Srinivas Pandruvada
2020-04-14 20:09 ` Jason A. Donenfeld
2020-04-14 20:23 ` Borislav Petkov
2020-04-14 20:49 ` Srinivas Pandruvada
2020-04-14 21:07 ` Jason A. Donenfeld
2020-04-14 21:51 ` Srinivas Pandruvada
2020-04-14 21:40 ` Peter Zijlstra
2020-04-14 21:44 ` Srinivas Pandruvada
2020-04-13 21:09 ` [PATCH 1/3] x86/mce/therm_throt: remove unused platform_thermal_notify function pointer Jason A. Donenfeld
2020-04-14 3:55 ` Srinivas Pandruvada
2020-04-14 4:21 ` Jason A. Donenfeld
2020-04-14 14:49 ` Srinivas Pandruvada [this message]
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=64f368b6bfde0611d3a1bc24884242bc4fb4cecd.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=Jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=bberg@redhat.com \
--cc=bp@suse.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).