Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: TAKANO Mitsuhiro <takano32@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Marc Zyngier <maz@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	linux-arm-kernel@lists.infradead.org,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	TAKANO Mitsuhiro <takano32@gmail.com>
Subject: [PATCH v2 0/2] arm64: errata: Fix two Kconfig column entries
Date: Sat, 21 Nov 2026 08:39:48 +0000	[thread overview]
Message-ID: <20261121083950.1957044-1-takano32@gmail.com> (raw)

Documentation/arch/arm64/silicon-errata.rst names two Kconfig symbols that
no Kconfig file defines.  I checked every Kconfig name in the table: these
are the only two.

The GIC-700 #2941627 entry names ARM64_ERRATUM_2941627; that workaround is
a GIC driver quirk, matched at runtime against the GIC's IIDR and enabled
through a static branch, so there is no symbol to name.  The Falkor E1041
entry names QCOM_FALKOR_ERRATUM_1041; the symbol defined in the tree is
QCOM_FALKOR_ERRATUM_E1041.

The two rows come from different commits, so they are kept separate and
each carries its own Fixes: tag.  Both are documentation-only changes: the
table keeps its column widths and no build was run.  I did not add a Cc:
stable tag, as nothing outside Documentation changes.

v2: the change is the same as in v1; only the index and hunk line numbers
moved with the rebase.  One changelog sentence is replaced in each patch:
in 1/2 v1 called the table row the tree's only record of the erratum, but
irq-gic-v3.c records it in gic_quirks[]; in 2/2 the sentence about the
symbol is reworded to name arch/arm64/Kconfig.  Both changelogs now say
that no build was run.

v1 was posted on 6 November 2026:
https://lore.kernel.org/all/20261106234541.1474324-1-takano32@gmail.com/
A duplicate submission went out the same night with different subjects on
1/2 and 2/2 (20261106235616.1533003); please ignore it.

The changes and the changelog text were produced with an AI coding
assistant (Hermes Agent, model deepseek-v4.1-flash) working from the tree
and the git history.  I reviewed the diff and the reasoning, and I am
responsible for the submission.

TAKANO Mitsuhiro (2):
  arm64: errata: Set GIC-700 #2941627 Kconfig entry to N/A
  arm64: errata: Fix Falkor E1041 Kconfig name

 Documentation/arch/arm64/silicon-errata.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


base-commit: d0f871bfb831705d9f55479f5b2b40f636ea7b16
-- 
2.53.0



             reply	other threads:[~2026-11-21  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-21  8:39 TAKANO Mitsuhiro [this message]
2026-11-21  8:39 ` [PATCH v2 1/2] arm64: errata: Set GIC-700 #2941627 Kconfig entry to N/A TAKANO Mitsuhiro
2026-11-21  8:39 ` [PATCH v2 2/2] arm64: errata: Fix Falkor E1041 Kconfig name TAKANO Mitsuhiro

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=20261121083950.1957044-1-takano32@gmail.com \
    --to=takano32@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=will@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