From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: linux-next: build warning after merge of the arm-soc tree
Date: Mon, 20 Jan 2014 10:39:53 +1100 [thread overview]
Message-ID: <20140120103953.329bd64dd540d547956ff46c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Hi all,
After merging the arm-soc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/pinctrl/pinconf.c: In function 'pinconf_pins_show':
drivers/pinctrl/pinconf.c:299:28: warning: unused variable 'ops' [-Wunused-variable]
const struct pinconf_ops *ops = pctldev->desc->confops;
^
drivers/pinctrl/pinconf.c: In function 'pinconf_groups_show':
drivers/pinctrl/pinconf.c:346:28: warning: unused variable 'ops' [-Wunused-variable]
const struct pinconf_ops *ops = pctldev->desc->confops;
^
Introduced by commit c420619d5177 ("pinctrl: pinconf: remove checks on
ops->pin_config_get").
Sorry, that I did not notice this earlier.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-01-19 23:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 23:39 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-22 0:48 linux-next: build warning after merge of the arm-soc tree Stephen Rothwell
2023-06-22 8:19 ` Arnd Bergmann
2023-06-22 8:26 ` Krzysztof Kozlowski
2023-06-22 13:55 ` Rob Herring
2021-12-22 21:59 Stephen Rothwell
2021-12-22 23:22 ` Arnd Bergmann
2021-12-22 23:58 ` Florian Fainelli
2021-12-23 8:50 ` Arınç ÜNAL
2021-12-23 18:18 ` Florian Fainelli
2021-10-25 23:39 Stephen Rothwell
2021-10-26 6:15 ` Joel Stanley
2022-01-20 3:22 ` Stephen Rothwell
2022-01-20 6:03 ` ChiaWei Wang
2021-04-06 0:45 Stephen Rothwell
2021-04-06 6:34 ` Krzysztof Kozlowski
2019-08-15 23:25 Stephen Rothwell
2019-08-15 23:23 Stephen Rothwell
2019-04-29 23:28 Stephen Rothwell
2019-05-03 6:49 ` Linus Walleij
2019-05-03 12:57 ` Arnd Bergmann
2012-03-19 7:39 Stephen Rothwell
2012-03-19 9:40 ` Arnd Bergmann
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=20140120103953.329bd64dd540d547956ff46c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
/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;
as well as URLs for NNTP newsgroup(s).