From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the rtc tree
Date: Wed, 21 Aug 2019 16:31:51 +1000 [thread overview]
Message-ID: <20190821163151.6e36d092@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
Hi all,
After merging the rtc tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/rtc/rtc-aspeed.c: In function 'aspeed_rtc_probe':
drivers/rtc/rtc-aspeed.c:89:6: warning: unused variable 'ret' [-Wunused-variable]
int ret;
^~~
drivers/rtc/rtc-armada38x.c: In function 'armada38x_rtc_probe':
drivers/rtc/rtc-armada38x.c:505:6: warning: unused variable 'ret' [-Wunused-variable]
int ret;
^~~
Introduced by commit
5a3a2836e8bf ("rtc: remove superfluous error message")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-08-21 6:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 6:31 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-23 5:24 linux-next: build warning after merge of the rtc tree Stephen Rothwell
2020-03-17 5:30 Stephen Rothwell
2019-10-30 4:41 Stephen Rothwell
2019-11-08 5:29 ` Stephen Rothwell
2019-11-08 15:20 ` Alexandre Belloni
2019-03-28 1:23 Stephen Rothwell
2019-03-28 1:36 ` Joel Stanley
2019-03-28 1:57 ` Alexandre Belloni
2019-03-28 2:09 ` Joel Stanley
2018-03-21 6:44 Stephen Rothwell
2017-07-06 4:24 Stephen Rothwell
2017-07-06 5:54 ` Heiner Kallweit
2017-07-06 6:59 ` Alexandre Belloni
2017-06-29 5:42 Stephen Rothwell
2017-01-13 3:18 Stephen Rothwell
2017-01-13 8:42 ` Amelie DELAUNAY
2017-01-10 3:01 Stephen Rothwell
2017-01-10 10:59 ` Alexandre Belloni
2016-07-11 8:12 Stephen Rothwell
2016-07-11 8:23 ` Uwe Kleine-König
2016-07-11 21:23 ` Alexandre Belloni
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=20190821163151.6e36d092@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexandre.belloni@bootlin.com \
--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.