linux-kernel - Re: [PATCH linux-next] thermal: int340x: processor

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] [day] [month] [year] [list]

Date:   Thu, 21 Sep 2023 11:36:43 +0200
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     srinivas pandruvada <srinivas.pandruvada@...ux.intel.com>
Cc:     "Rafael J. Wysocki" <rafael@...nel.org>, daniel.lezcano@...aro.org,
        rui.zhang@...el.com, linux-pm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH linux-next] thermal: int340x: processor_thermal: Ack all
 PCI interrupts

On Wed, Sep 20, 2023 at 9:29 PM srinivas pandruvada
<srinivas.pandruvada@...ux.intel.com> wrote:
>
> On Wed, 2023-09-20 at 21:21 +0200, Rafael J. Wysocki wrote:
> > On Wed, Sep 20, 2023 at 8:52 PM Srinivas Pandruvada
> > <srinivas.pandruvada@...ux.intel.com> wrote:
> > >
> > > All interrupts from the processor thermal PCI device requires ACK.
> > > This
> > > is done by writing 0x01 at offset 0xDC in the config space. This is
> > > already done for the thereshold interrupt. Extend this for the
> > > workload
> > > hint interrupt.
> > >
> > > Signed-off-by: Srinivas Pandruvada
> > > <srinivas.pandruvada@...ux.intel.com>
> >
> > Is this a fix for one of the commits in linux-next?  If so, which
> > one?
> This is on top of workload hints patches.  I marked linux-next as they
> are not in mainline kernel.
>
> This can alternatively merged to
> e682b86211a1 thermal: int340x: Handle workload hint interrupts
>
> But not sure how to mark the commit id as they will change.

As a rule, commits in my linux-next branch don't change (they
sometimes change, but that is not a common case), so you can use the
current one.  If it changes, I'll update the tag accordingly.

I'm going to add a Fixes: tag pointing to the above commit to it.

Thanks!