From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
Thierry Reding <treding@nvidia.com>
Cc: Bitan Biswas <bbiswas@nvidia.com>,
Jon Hunter <jonathanh@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the tegra tree
Date: Mon, 27 Jun 2022 09:15:19 +1000 [thread overview]
Message-ID: <20220627091519.323d5a82@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
Hi all,
After merging the tegra tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from drivers/soc/tegra/fuse/fuse-tegra.c:7:
include/linux/device.h:136:33: warning: 'dev_attr_production' defined but not used [-Wunused-variable]
136 | struct device_attribute dev_attr_##_name = __ATTR_RO(_name)
| ^~~~~~~~~
drivers/soc/tegra/fuse/fuse-tegra.c:441:8: note: in expansion of macro 'DEVICE_ATTR_RO'
441 | static DEVICE_ATTR_RO(production);
| ^~~~~~~~~~~~~~
Introduced by commit
2258fe488a20 ("soc/tegra: fuse: Expose Tegra production status")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-06-26 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 23:15 Stephen Rothwell [this message]
2022-06-27 11:53 ` linux-next: build warning after merge of the tegra tree Jon Hunter
-- strict thread matches above, loose matches on Subject: below --
2023-07-21 3:07 Stephen Rothwell
2021-06-03 0:35 Stephen Rothwell
2021-06-03 2:01 ` Dmitry Osipenko
2021-06-03 12:18 ` Thierry Reding
2021-06-03 14:03 ` Dmitry Osipenko
2021-06-03 14:35 ` Thierry Reding
2021-06-03 14:37 ` Dmitry Osipenko
2015-05-07 4:06 Stephen Rothwell
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=20220627091519.323d5a82@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bbiswas@nvidia.com \
--cc=ccross@android.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--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