From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-tegra@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Kartik <kkartik@nvidia.com>
Subject: Re: linux-next: Tree for Jan 29 (soc/tegra/fuse/fuse-tegra30.c)
Date: Mon, 29 Jan 2024 20:06:14 -0800 [thread overview]
Message-ID: <d0e1a7c1-06a2-4fa4-b4f8-df149af8eccb@infradead.org> (raw)
In-Reply-To: <20240129143030.16647483@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On 1/28/24 19:30, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20240125:
>
on arm64:
../drivers/soc/tegra/fuse/fuse-tegra30.c:684:17: error: 'tegra30_fuse_read' undeclared here (not in a function); did you mean 'tegra_fuse_readl'?
684 | .read = tegra30_fuse_read,
| ^~~~~~~~~~~~~~~~~
| tegra_fuse_readl
../drivers/soc/tegra/fuse/fuse-tegra30.c:694:17: error: 'tegra30_fuse_init' undeclared here (not in a function); did you mean 'tegra_fuse_info'?
694 | .init = tegra30_fuse_init,
| ^~~~~~~~~~~~~~~~~
| tegra_fuse_info
Full randconfig file is attached.
--
#Randy
[-- Attachment #2: config-r5887.gz --]
[-- Type: application/gzip, Size: 45378 bytes --]
next parent reply other threads:[~2024-01-30 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240129143030.16647483@canb.auug.org.au>
2024-01-30 4:06 ` Randy Dunlap [this message]
2024-01-30 10:46 ` linux-next: Tree for Jan 29 (soc/tegra/fuse/fuse-tegra30.c) Jon Hunter
2024-01-30 10:59 ` Arnd Bergmann
2024-01-30 11:02 ` Jon Hunter
2024-02-01 15:07 ` 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=d0e1a7c1-06a2-4fa4-b4f8-df149af8eccb@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=kkartik@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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