From: Stian Halseth <stian@itx.no>
To: sashiko-reviews@lists.linux.dev, sparclinux@vger.kernel.org
Cc: Andreas Larsson <andreas@gaisler.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Biggers <ebiggers@kernel.org>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] sparc64: Stop the hwcap-list parser at an unterminated entry
Date: Wed, 18 Nov 2026 13:53:19 +0100 [thread overview]
Message-ID: <fead846b415ddff4e2a97acff37c3dc40c107d3c.camel@itx.no> (raw)
In-Reply-To: <sashiko-outbox-220876@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
Hi Andreas,
On Wed, 2026-11-18 at 12:07 +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
>
> [Severity: Low]
> This fixes a bug in mdesc_cpu_hwcap_list(). Should this include:
>
> Fixes: ac85fe8b2124 ("sparc: Sanitize cpu feature detection and reporting.")
>
Yes, the loop came in with that commit.
Fixes: ac85fe8b2124 ("sparc: Sanitize cpu feature detection and reporting.")
Could you add it when applying? If there is a v3, I'll fold it in.
/Stian
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-11-18 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 11:55 [PATCH v2 0/2] sparc64: Read qemu,hwcap-list on sun4u Stian Halseth
2026-11-18 11:55 ` [PATCH v2 1/2] sparc64: Stop the hwcap-list parser at an unterminated entry Stian Halseth
[not found] ` <sashiko-outbox-220876@kernel.org>
2026-11-18 12:53 ` Stian Halseth [this message]
2026-11-18 11:55 ` [PATCH v2 2/2] sparc64: Read qemu,hwcap-list from the OF cpu node on sun4u Stian Halseth
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=fead846b415ddff4e2a97acff37c3dc40c107d3c.camel@itx.no \
--to=stian@itx.no \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sparclinux@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®