From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Hans de Goede <hansg@kernel.org>,
"open list:AMD HETERO CORE HARDWARE FEEDBACK DRIVER"
<platform-driver-x86@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Fix a few Sashiko flagged issues on AMD_HFI
Date: Mon, 21 Sep 2026 20:22:59 +0300 (EEST) [thread overview]
Message-ID: <a82ef9e8-7c71-0638-bf2f-b354a1ec62c6@linux.intel.com> (raw)
In-Reply-To: <92a0c8c3-3db1-4252-9c84-9a91ca8681c7@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
On Mon, 21 Sep 2026, Mario Limonciello wrote:
> On 9/21/26 12:10, Ilpo Järvinen wrote:
> > On Mon, 21 Sep 2026, Mario Limonciello wrote:
> >
> > > Sashiko flagged a few instances that could trigger out of bounds or
> > > use-after-free. This series fixes them.
> >
> > Hi,
> >
> > I suppose it would be fair to credit sashiko with tags.
> >
> > > Mario Limonciello (3):
> > > platform/x86/amd: hfi: Fix a use-after-free when unloading the driver
> > > platform/x86/amd: hfi: Fix out-of-bounds reads when parsing ranking
> > > data
> > > platform/x86/amd: hfi: Rely on ACPI enumeration instead of a dummy
> > > device
> > >
> > > drivers/platform/x86/amd/hfi/hfi.c | 34 ++++++++++++++++++------------
> > > 1 file changed, 21 insertions(+), 13 deletions(-)
> > >
> > >
> >
>
> What tag would I use? The Sashiko URLs appear to be private (or at least I
> need to be logged in).
>
> Something like:
>
> Reported-by: Sashiko
>
> or
>
> Reported-by: Sashiko
> Closes: <private-sashiko-url>
People have used:
Reported-by: Sashiko <sashiko-bot@kernel.org>
+ Closes tag
For the publically reviewed patches, the patches and their comments can be
looked up from https://sashiko.dev . I'm not logged anywhere and can
access at least those urls just fine. But if you for some reason cannot
find a working link (w/o requiring login), we can just leave the Closes
tag out.
--
i.
next prev parent reply other threads:[~2026-09-21 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 17:04 Mario Limonciello
2026-09-21 17:04 ` [PATCH 1/3] platform/x86/amd: hfi: Fix a use-after-free when unloading the driver Mario Limonciello
2026-09-21 17:26 ` Mario Limonciello
2026-09-21 17:04 ` [PATCH 2/3] platform/x86/amd: hfi: Fix out-of-bounds reads when parsing ranking data Mario Limonciello
2026-09-21 17:27 ` Mario Limonciello
2026-09-21 17:04 ` [PATCH 3/3] platform/x86/amd: hfi: Rely on ACPI enumeration instead of a dummy device Mario Limonciello
2026-09-21 17:27 ` Mario Limonciello
2026-09-21 17:10 ` [PATCH 0/3] Fix a few Sashiko flagged issues on AMD_HFI Ilpo Järvinen
2026-09-21 17:13 ` Mario Limonciello
2026-09-21 17:22 ` Ilpo Järvinen [this message]
2026-09-21 17:26 ` Mario Limonciello
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=a82ef9e8-7c71-0638-bf2f-b354a1ec62c6@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.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
all inboxes | Powered by JetHome®