From: Marek Vasut <marex@denx.de>
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>,
Johan Hovold <johan@kernel.org>
Subject: Re: linux-next: build failure after merge of the tty.current tree
Date: Thu, 19 Jan 2023 22:49:19 +0100 [thread overview]
Message-ID: <fea0fa6e-c2c6-f904-4e9b-94f40fa443ea@denx.de> (raw)
In-Reply-To: <20230120075832.02bc1124@canb.auug.org.au>
On 1/19/23 21:58, Stephen Rothwell wrote:
> Hi all,
Hi,
> After merging the tty.current tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/tty/serial/stm32-usart.c: In function 'stm32_usart_interrupt':
> drivers/tty/serial/stm32-usart.c:804:62: error: 'flags' undeclared (first use in this function)
> 804 | uart_unlock_and_check_sysrq_irqrestore(port, flags);
> | ^~~~~
> drivers/tty/serial/stm32-usart.c:804:62: note: each undeclared identifier is reported only once for each function it appears in
>
> Caused by commit
>
> f24771b62a83 ("serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ handler")
>
> I have used the tty.current tree from next-20230119 for today.
I already proposed a fix in the build robot report
[tty:tty-linus 4/7] drivers/tty/serial/stm32-usart.c:804:62: error:
'flags' undeclared
Now waiting for Johan to confirm that's the correct approach.
next prev parent reply other threads:[~2023-01-19 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 20:58 linux-next: build failure after merge of the tty.current tree Stephen Rothwell
2023-01-19 21:49 ` Marek Vasut [this message]
2023-01-21 7:30 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2014-07-11 1:21 Stephen Rothwell
2014-07-11 15:06 ` Peter Hurley
2014-07-12 1:20 ` Stephen Rothwell
2014-07-12 13:02 ` Peter Hurley
2014-07-15 17:49 ` Peter Hurley
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=fea0fa6e-c2c6-f904-4e9b-94f40fa443ea@denx.de \
--to=marex@denx.de \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.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).