mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Oded Gabbay <ogabbay@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Linux 5.18-rc1
Date: Mon, 4 Apr 2022 08:01:14 +0200	[thread overview]
Message-ID: <694a8729-7313-e63e-7415-5a749be3a828@suse.cz> (raw)
In-Reply-To: <CAHk-=wimc7V9mi=P+6p2nnctPYtSM55OSPVERUeJor7fkD_EVg@mail.gmail.com>

On 04. 04. 22, 5:29, Linus Torvalds wrote:
>> Error log:
>> drivers/tty/serial/mpc52xx_uart.c:967:23: error: initialization of 'unsigned int (*)(struct uart_port *)' from incompatible pointer type 'int (*)(struct uart_port *)' [-Werror=incompatible-pointer-types]
>>    967 |         .raw_rx_rdy = mpc5125_psc_raw_rx_rdy,
>>
>> and many similar errors.
>>
>> Caused by commit 18662a1d8f35 ("tty: serial: mpc52xx_uart: make rx/tx
>> hooks return unsigned"). Reported at
>> https://lore.kernel.org/lkml/20220403153607.GA3644508@roeck-us.net/
> 
> Jiri - apparently you didn't convert the cases under CONFIG_PPC_MPC512x.
> 
> Please, people, let's get these silly problems fixed asap, and not
> have people unaware of them and fixes pending until much later in the
> rc series? It was painful  last release, let's not repeat that
> mistake.

Sure, I wasn't aware of the issue until yesterday -- when Guenter 
dropped me an e-mail. It passed through all the testing machinery which 
is unfortunate. (I have a script to cross-compile most of the peculiar 
tty drivers [1]. That indeed contains "mpc52xx_uart.o powerpc_mpc5200".) 
The fix was posted as 20220404055122.31194-1-jslaby@suse.cz .

[1] https://pastebin.com/UDTsBAaY

thanks,
-- 
js
suse labs

  parent reply	other threads:[~2022-04-04  6:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 22:14 Linus Torvalds
2022-04-04  2:22 ` Guenter Roeck
2022-04-04  3:29   ` Linus Torvalds
2022-04-04  4:23     ` Guenter Roeck
2022-04-04  7:30       ` Ron Economos
2022-04-04 15:32       ` Linus Torvalds
2022-04-04 16:21         ` Greg Kroah-Hartman
2022-04-04 16:45         ` Guenter Roeck
2022-04-04 17:09           ` Linus Torvalds
2022-04-05 21:14           ` Konstantin Ryabitsev
2022-04-04  6:01     ` Jiri Slaby [this message]
2022-04-05 12:19   ` Sudip Mukherjee
2022-04-05 13:18     ` Guenter Roeck
2022-04-04  7:47 ` Build regressions/improvements in v5.18-rc1 Geert Uytterhoeven
2022-04-04  8:16   ` Geert Uytterhoeven
2022-04-04  9:26     ` Dave Chinner
2022-04-04 10:19       ` Geert Uytterhoeven
2022-04-04 11:45         ` Arnd Bergmann
2022-04-04 12:31           ` Arnd Bergmann
2022-04-04 22:16           ` Dave Chinner
2022-04-05  6:47             ` Geert Uytterhoeven
2022-04-05  7:08               ` Arnd Bergmann
2022-04-05 21:05                 ` Dave Chinner
2022-04-04 18:39     ` Kalle Valo
2022-04-05  6:46       ` Geert Uytterhoeven
2022-04-05  6:52         ` Kalle Valo
2022-04-05  6:45     ` Helge Deller
2022-04-05  6:49       ` Geert Uytterhoeven
2022-04-28  7:25         ` Michael Ellerman

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=694a8729-7313-e63e-7415-5a749be3a828@suse.cz \
    --to=jslaby@suse.cz \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=ogabbay@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®