From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Stanley Subject: Re: linux-next: build warning after merge of the rtc tree Date: Thu, 28 Mar 2019 02:09:35 +0000 Message-ID: References: <20190328122300.02fc46c4@canb.auug.org.au> <20190328015733.GI21724@piout.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20190328015733.GI21724@piout.net> Sender: linux-kernel-owner@vger.kernel.org To: Alexandre Belloni Cc: Stephen Rothwell , Linux Next Mailing List , Linux Kernel Mailing List List-Id: linux-next.vger.kernel.org On Thu, 28 Mar 2019 at 01:59, Alexandre Belloni wrote: > > On 28/03/2019 01:36:21+0000, Joel Stanley wrote: > > On Thu, 28 Mar 2019 at 01:23, Stephen Rothwell 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. Thanks! (Sorry, I fat fingered v3 and then prepared a v4 but didn't send it. The only change was removing the flags variable.)