public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Laura Abbott <labbott@redhat•com>,
	Daniel Thompson <daniel.thompson@linaro•org>
Subject: linux-next: build warning after merge of the tty tree
Date: Wed, 19 Sep 2018 13:12:08 +1000	[thread overview]
Message-ID: <20180919131208.07aa9c6b@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 407 bytes --]

Hi Greg,

After merging the tty tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:

drivers/tty/serial/kgdboc.c:134:12: warning: 'kgdboc_option_setup' defined but not used [-Wunused-function]
 static int kgdboc_option_setup(char *opt)
            ^~~~~~~~~~~~~~~~~~~

Introduced by commit

  2dd453168643 ("kgdboc: Fix restrict error")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2018-09-19  3:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  3:12 Stephen Rothwell [this message]
2018-09-20  1:59 ` [PATCH] kgdboc: Fix warning with module build Laura Abbott
2018-09-20  7:16   ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2025-06-24  6:39 linux-next: build warning after merge of the tty tree 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-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=20180919131208.07aa9c6b@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=daniel.thompson@linaro$(echo .)org \
    --cc=greg@kroah$(echo .)com \
    --cc=labbott@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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