From: broonie@kernel.org
To: Linus Walleij <linus.walleij@linaro.org>,
Mario Limonciello <mario.limonciello@amd.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-gpio@vger.kernel.org
Subject: linux-next: build failure after merge of the pinctrl tree
Date: Tue, 2 Aug 2022 23:21:37 +0100 [thread overview]
Message-ID: <20220802222137.2435761-1-broonie@kernel.org> (raw)
Hi all,
After merging the pinctrl-samsung tree, today's linux-next build
(x86 allmodconfig) failed like this:
/tmp/next/build/drivers/pinctrl/pinctrl-amd.c: In function 'amd_gpio_dbg_show':
/tmp/next/build/drivers/pinctrl/pinctrl-amd.c:219:8: error: unused variable 'output_enable' [-Werror=unused-variable]
219 | char *output_enable;
| ^~~~~~~~~~~~~
cc1: all warnings being treated as errors
Caused by commit
e8129a076a509c ("pinctrl: amd: Use unicode for debugfs output")
I have reverted that commit for today.
next reply other threads:[~2022-08-02 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 22:21 broonie [this message]
2022-08-02 22:29 ` linux-next: build failure after merge of the pinctrl tree Mario Limonciello
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=20220802222137.2435761-1-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mario.limonciello@amd.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