lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9rOzmF4K965U69tFZi2SS3rW9SHed2bJ=_PD+xu8LqMYw@mail.gmail.com>
Date:   Mon, 13 Apr 2020 22:21:47 -0600
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Cc:     LKML <linux-kernel@...r.kernel.org>, linux-edac@...r.kernel.org,
        X86 ML <x86@...nel.org>, Arnd Bergmann <arnd@...db.de>,
        bberg@...hat.com, bp@...e.de
Subject: Re: [PATCH 1/3] x86/mce/therm_throt: remove unused
 platform_thermal_notify function pointer

On Mon, Apr 13, 2020 at 9:56 PM Srinivas Pandruvada
<srinivas.pandruvada@...ux.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? If not, how do your thermal patches
usually go in? A reviewed-by might be useful in that case.

Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ