From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Joel Stanley <joel@jms.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the rtc tree
Date: Thu, 28 Mar 2019 02:57:33 +0100 [thread overview]
Message-ID: <20190328015733.GI21724@piout.net> (raw)
In-Reply-To: <CACPK8Xdx5TtG=7ZTgRg_V=obawreGrTG-aA2gESjpxcQY-wOBg@mail.gmail.com>
On 28/03/2019 01:36:21+0000, Joel Stanley wrote:
> On Thu, 28 Mar 2019 at 01:23, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > 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_read_time':
> > drivers/rtc/rtc-aspeed.c:26:16: warning: unused variable 'flags' [-Wunused-variable]
> > unsigned long flags;
> > ^~~~~
> > drivers/rtc/rtc-aspeed.c: In function 'aspeed_rtc_set_time':
> > drivers/rtc/rtc-aspeed.c:57:16: warning: unused variable 'flags' [-Wunused-variable]
> > unsigned long flags;
> > ^~~~~
> >
> > Introduced by commit
> >
> > 7f4d485413fb ("rtc: Add ASPEED RTC driver")
>
> Alexandre, it looks like v3 went in instead of v4. Do you need me to
> send a follow up?
>
I didn't get any v4, I'll fix it up in the tree.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-28 1:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 1:23 linux-next: build warning after merge of the rtc tree Stephen Rothwell
2019-03-28 1:36 ` Joel Stanley
2019-03-28 1:57 ` Alexandre Belloni [this message]
2019-03-28 2:09 ` Joel Stanley
-- strict thread matches above, loose matches on Subject: below --
2020-03-23 5:24 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-08-21 6:31 Stephen Rothwell
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=20190328015733.GI21724@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).