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,
Ulrich Hecht <ulrich.hecht+renesas@gmail•com>,
Geert Uytterhoeven <geert+renesas@glider•be>
Subject: linux-next: build warning after merge of the tty tree
Date: Mon, 6 Feb 2017 15:16:38 +1100 [thread overview]
Message-ID: <20170206151638.6e0f8a60@canb.auug.org.au> (raw)
Hi Greg,
After merging the tty tree, today's linux-next build
(arm_multi_v7_defconfig) produced this warning:
drivers/tty/serial/sh-sci.c:977:12: warning: 'scif_set_rtrg' defined but not used [-Wunused-function]
static int scif_set_rtrg(struct uart_port *port, int rx_trig)
^
Introduced by commit
a380ed461f66 ("serial: sh-sci: implement FIFO threshold register setting")
Forgot to add a call to this new function?
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-02-06 4:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 4:16 Stephen Rothwell [this message]
2017-02-06 8:50 ` linux-next: build warning after merge of the tty tree 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
-- strict thread matches above, loose matches on Subject: below --
2025-06-24 6:39 Stephen Rothwell
2025-06-24 7:58 ` Jiri Slaby
2024-08-07 3:44 Stephen Rothwell
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
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=20170206151638.6e0f8a60@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=geert+renesas@glider$(echo .)be \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ulrich.hecht+renesas@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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