From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>, Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the tty tree
Date: Sun, 6 Nov 2022 19:47:23 -0800 [thread overview]
Message-ID: <202211061946.AC6355E1C@keescook> (raw)
In-Reply-To: <20221107143434.66f7be35@canb.auug.org.au>
On Mon, Nov 07, 2022 at 02:34:34PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tty tree, today's linux-next build (htmldocs) produced
> this warning:
>
> drivers/tty/tty_io.c:2271: warning: cannot understand function prototype: 'bool tty_legacy_tiocsti __read_mostly = IS_ENABLED(CONFIG_LEGACY_TIOCSTI); '
>
> Introduced by commit
>
> 83efeeeb3d04 ("tty: Allow TIOCSTI to be disabled")
Whoops! Thank you for the report. I've sent a fix:
https://lore.kernel.org/lkml/20221107034631.never.637-kees@kernel.org
-Kees
--
Kees Cook
next prev parent reply other threads:[~2022-11-07 3:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 3:34 linux-next: build warning after merge of the tty tree Stephen Rothwell
2022-11-07 3:47 ` Kees Cook [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=202211061946.AC6355E1C@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--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.