From: "Thierry Reding" <thierry.reding@gmail.com>
To: "Arnd Bergmann" <arnd@arndb.de>,
"Jon Hunter" <jonathanh@nvidia.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"linux-next" <linux-next@vger.kernel.org>,
"Kartik" <kkartik@nvidia.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"Thierry Reding" <treding@nvidia.com>
Subject: Re: linux-next: Tree for Jan 29 (soc/tegra/fuse/fuse-tegra30.c)
Date: Thu, 01 Feb 2024 16:07:08 +0100 [thread overview]
Message-ID: <CYTU44ED147E.2V11E1VTOPYSE@gmail.com> (raw)
In-Reply-To: <dafa2fb5-276d-4c87-b003-4b7f30d44f0a@app.fastmail.com>
On Tue Jan 30, 2024 at 11:59 AM CET, Arnd Bergmann wrote:
> On Tue, Jan 30, 2024, at 11:46, Jon Hunter wrote:
> > On 30/01/2024 04:06, Randy Dunlap wrote:
>
> > Looks like we are missing the following ...
> >
> > diff --git a/drivers/soc/tegra/fuse/fuse-tegra30.c
> > b/drivers/soc/tegra/fuse/fuse-tegra30.c
> > index 2070d36c510d..eb14e5ff5a0a 100644
> > --- a/drivers/soc/tegra/fuse/fuse-tegra30.c
> > +++ b/drivers/soc/tegra/fuse/fuse-tegra30.c
> > @@ -38,7 +38,8 @@
> > defined(CONFIG_ARCH_TEGRA_210_SOC) || \
> > defined(CONFIG_ARCH_TEGRA_186_SOC) || \
> > defined(CONFIG_ARCH_TEGRA_194_SOC) || \
> > - defined(CONFIG_ARCH_TEGRA_234_SOC)
> > + defined(CONFIG_ARCH_TEGRA_234_SOC) || \
> > + defined(CONFIG_ARCH_TEGRA_241_SOC)
> > static u32 tegra30_fuse_read_early(struct tegra_fuse *fuse, unsigned
> > int offset)
> >
> >
> > Kartik, can you send a fix for this?
>
> If I get an Ack for my original patch, I can pick that
> up into the soc tree directly:
>
> https://lore.kernel.org/all/20240103102654.3779458-1-arnd@kernel.org/
Sorry for the delay on this. I guess you can't really apply that to ARM
SoC directly because the patch that introduces Tegra241 support is only
in the Tegra tree.
In any case, I've applied your patch now, so the fixed version should
show up in tomorrow's linux-next.
I'm considering squashing it into the original since that'd preserve
bisectability, though that'd probably be of limited usefulness because
most people doing regression builds involving this will likely have one
of the other bits enabled.
Thierry
prev parent reply other threads:[~2024-02-01 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 3:30 linux-next: Tree for Jan 29 Stephen Rothwell
2024-01-30 3:50 ` linux-next: Tree for Jan 29 (fs/Kconfig: HUGETLBFS) Randy Dunlap
2024-01-30 3:55 ` linux-next: Tree for Jan 29 (drm/xe/ and FB_IOMEM_HELPERS) Randy Dunlap
2024-01-30 4:06 ` linux-next: Tree for Jan 29 (soc/tegra/fuse/fuse-tegra30.c) Randy Dunlap
2024-01-30 10:46 ` Jon Hunter
2024-01-30 10:59 ` Arnd Bergmann
2024-01-30 11:02 ` Jon Hunter
2024-02-01 15:07 ` Thierry Reding [this message]
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=CYTU44ED147E.2V11E1VTOPYSE@gmail.com \
--to=thierry.reding@gmail.com \
--cc=arnd@arndb.de \
--cc=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=treding@nvidia.com \
/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