All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: build warning after merge of the tty tree
Date: Mon, 6 Feb 2017 09:50:42 +0100	[thread overview]
Message-ID: <20170206085042.GA3726@kroah.com> (raw)
In-Reply-To: <20170206151638.6e0f8a60@canb.auug.org.au>

On Mon, Feb 06, 2017 at 03:16:38PM +1100, Stephen Rothwell wrote:
> 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?

I think this is fixed by a patch I just took into my tree, which isn't
in linux-next yet.  Right Ulrich?  Or is this still a warning with your
latest patch series?

thanks,

greg k-h

  reply	other threads:[~2017-02-06  8:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  4:16 linux-next: build warning after merge of the tty tree Stephen Rothwell
2017-02-06  8:50 ` Greg KH [this message]
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=20170206085042.GA3726@kroah.com \
    --to=greg@kroah.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=ulrich.hecht+renesas@gmail.com \
    /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.