From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: linux-next: build warning after merge of the pinctrl tree
Date: Fri, 13 Dec 2013 15:06:43 +1100 [thread overview]
Message-ID: <20131213150643.51342b68314f2d6b201e54dd@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
Hi Linus,
After merging the pinctrl 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").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-12-13 4:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 4:06 Stephen Rothwell [this message]
2014-05-19 6:59 linux-next: build warning after merge of the pinctrl tree Stephen Rothwell
2014-05-19 9:03 ` Maxime Ripard
2015-05-20 6:40 Stephen Rothwell
2015-05-20 7:14 ` Linus Walleij
2017-01-03 4:37 Stephen Rothwell
2017-06-30 4:56 Stephen Rothwell
2017-06-30 4:57 ` Stephen Rothwell
2017-06-30 6:59 ` Geert Uytterhoeven
2017-06-30 13:48 ` Linus Walleij
2018-10-11 3:17 Stephen Rothwell
2018-10-11 7:51 ` Linus Walleij
2020-04-17 2:27 Stephen Rothwell
2020-04-17 10:23 ` Linus Walleij
2021-03-30 6:07 Stephen Rothwell
2021-03-30 7:51 ` Linus Walleij
2021-10-27 11:01 Stephen Rothwell
2021-10-27 11:10 ` Marc Zyngier
2021-10-28 7:03 ` Mauro Carvalho Chehab
2022-01-20 3:25 ` Stephen Rothwell
2022-03-18 7:31 ` Stephen Rothwell
2022-06-05 23:33 ` Stephen Rothwell
2022-04-21 7:11 Stephen Rothwell
2022-04-21 14:12 ` Linus Walleij
2022-04-21 18:05 ` Stefan Wahren
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=20131213150643.51342b68314f2d6b201e54dd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexandre.belloni@free-electrons.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.