All of lore.kernel.org
 help / color / mirror / Atom feed
From: miaoqinglang <miaoqinglang@huawei.com>
To: Greg KH <greg@kroah.com>
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 tty tree
Date: Tue, 29 Sep 2020 14:41:27 +0800	[thread overview]
Message-ID: <2e36e978-1276-6b86-3956-4346fc04093f@huawei.com> (raw)
In-Reply-To: <20200929160111.18719071@canb.auug.org.au>



在 2020/9/29 14:01, Stephen Rothwell 写道:
> Hi all,
> 
> After merging the tty tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
> 
> drivers/tty/serial/mvebu-uart.c: In function 'mvebu_uart_probe':
> drivers/tty/serial/mvebu-uart.c:806:6: warning: unused variable 'ret' [-Wunused-variable]
>    806 |  int ret, id, irq;
>        |      ^~~
> 
> Introduced by commit
> 
>    b63537020db3 ("serial: mvebu-uart: simplify the return expression of mvebu_uart_probe()")
> 
Hi Greg,

Sorry about the noise for remaining the unused variable 'ret' in commit 
b63537020db3.

Should I send another patch to clean up this warning or send another v2 
patch instead?

Thanks.

  reply	other threads:[~2020-09-29  6:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  6:01 linux-next: build warning after merge of the tty tree Stephen Rothwell
2020-09-29  6:41 ` miaoqinglang [this message]
2020-09-29  7:32   ` Greg KH
2020-09-29  8:58     ` miaoqinglang
  -- strict thread matches above, loose matches on Subject: below --
2022-11-07  3:34 Stephen Rothwell
2022-11-07  3:47 ` Kees Cook
2022-04-20  6:32 Stephen Rothwell
2022-04-19  6:33 Stephen Rothwell
2022-04-19  6:35 ` Stephen Rothwell
2022-04-19  6:36   ` Jiri Slaby
2022-04-19  6:35 ` Jiri Slaby
2020-09-09  5:56 Stephen Rothwell
2020-09-09  7:41 ` Greg KH
2018-09-19  3:12 Stephen Rothwell
2018-07-23  5:39 Stephen Rothwell
2018-07-23  9:03 ` Andy Shevchenko
2017-02-06  4:16 Stephen Rothwell
2017-02-06  8:50 ` Greg KH
2017-02-06 17:01   ` Ulrich Hecht
2017-02-06 22:37     ` Stephen Rothwell
2017-02-07  8:37       ` Greg KH
2017-02-07 11:18         ` Stephen Rothwell
2016-01-21  1:56 Stephen Rothwell
2016-01-21  2:07 ` Greg KH
2015-03-10  5:28 Stephen Rothwell
2015-03-10  8:23 ` Uwe Kleine-König
2015-03-10  9:19   ` Greg KH
2010-09-24  4:03 Stephen Rothwell
2010-09-24  4:44 ` Greg KH

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=2e36e978-1276-6b86-3956-4346fc04093f@huawei.com \
    --to=miaoqinglang@huawei.com \
    --cc=greg@kroah.com \
    --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 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.