From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: linux-next: build warning after merge of the tty tree
Date: Thu, 21 Jan 2016 12:56:18 +1100 [thread overview]
Message-ID: <20160121125618.78f0cb37@canb.auug.org.au> (raw)
Hi Greg,
After merging the tty tree (now in Linus' tree, sorry for not pointing
it out earlier), today's linux-next build (multi_v7_defconfig) produced
this warning:
drivers/tty/serial/amba-pl011.c:190:27: warning: 'vendor_zte' defined but not used [-Wunused-variable]
static struct vendor_data vendor_zte = {
^
Introduced by commit
7ec758718920 ("tty: amba-pl011: add support for ZTE UART (EXPERIMENTAL)")
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
next reply other threads:[~2016-01-21 1:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 1:56 Stephen Rothwell [this message]
2016-01-21 2:07 ` linux-next: build warning after merge of the tty tree Greg KH
-- 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-29 6:01 Stephen Rothwell
2020-09-29 6:41 ` miaoqinglang
2020-09-29 7:32 ` Greg KH
2020-09-29 8:58 ` miaoqinglang
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
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=20160121125618.78f0cb37@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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.