From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thierry Reding" <thierry.reding@kernel.org>,
arm <arm@kernel.org>,
soc@kernel.org
Cc: "Jon Hunter" <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Sasha Levin" <sashal@kernel.org>
Subject: Re: [GIT PULL 4/6] firmware: tegra: Changes for v7.2-rc1
Date: Tue, 09 Jun 2026 16:38:02 +0200 [thread overview]
Message-ID: <7c575b6d-5543-42e8-9b7c-be1e7148c454@app.fastmail.com> (raw)
In-Reply-To: <20260531060825.1855391-4-thierry.reding@kernel.org>
On Sun, May 31, 2026, at 08:08, Thierry Reding wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
> ----------------------------------------------------------------
> Jon Hunter (2):
> firmware: tegra: bpmp: Propagate debugfs errors
> firmware: tegra: bpmp: Add support for multi-socket platforms
>
> Sasha Levin (1):
> firmware: tegra: Make TEGRA_IVC a hidden Kconfig symbol
I'm merging this, but I would like to point out that the third
patch does not actually solve a real problem and the patch
description is complete nonsense.
Looking through linux-next, I see two more of Sasha's patches
addressing kconfiglint 'K002' warnings. I have not used that
tool and the warning sounds useful in general, but all three
of these patches look like false positives.
Sasha, please try to understand better what the tool is
trying to warn about.
Arnd
next prev parent reply other threads:[~2026-06-09 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 6:08 [GIT PULL 1/6] dt-bindings: Changes for v7.2-rc1 Thierry Reding
2026-05-31 6:08 ` [GIT PULL 2/6] soc/tegra: " Thierry Reding
2026-05-31 6:08 ` [GIT PULL 3/6] soc/tegra: pmc: " Thierry Reding
2026-05-31 6:08 ` [GIT PULL 4/6] firmware: tegra: " Thierry Reding
2026-06-09 14:38 ` Arnd Bergmann [this message]
2026-05-31 6:08 ` [GIT PULL 5/6] ARM: tegra: Device tree changes " Thierry Reding
2026-05-31 6:08 ` [GIT PULL 6/6] arm64: tegra: Changes " Thierry Reding
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=7c575b6d-5543-42e8-9b7c-be1e7148c454@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=soc@kernel.org \
--cc=thierry.reding@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