linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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: Tue, 24 Jun 2025 09:58:59 +0200	[thread overview]
Message-ID: <bdda29d8-f30d-47e3-987f-a2cdb855f4d0@kernel.org> (raw)
In-Reply-To: <20250624163933.301e7859@canb.auug.org.au>

On 24. 06. 25, 8:39, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the tty tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> drivers/tty/tty_port.c:400: warning: expecting prototype for tty_port_tty_hangup(). Prototype was for __tty_port_tty_hangup() instead
> 
> Introduced by commit
> 
>    2b5eac0f8c6e ("tty: introduce and use tty_port_tty_vhangup() helper")

I noticed, fix sent yesterday:
https://lore.kernel.org/all/20250623074606.456532-6-jirislaby@kernel.org/

I need to respin and send a v2 of the series.

thanks,
-- 
js
suse labs

  reply	other threads:[~2025-06-24  7:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24  6:39 linux-next: build warning after merge of the tty tree Stephen Rothwell
2025-06-24  7:58 ` Jiri Slaby [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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=bdda29d8-f30d-47e3-987f-a2cdb855f4d0@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).