Issues building RT patchset v6.18.13-rt4-rebase on top of v6.18.39

Issues building RT patchset v6.18.13-rt4-rebase on top of v6.18.39

[David Runge]

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

Hi,

on Arch Linux we have switched to a rebase workflow to offer the linux-rt [1]
and linux-rt-lts [2] kernels on latest kernels of the series, so that we can
also apply security and regression fixes.

For linux-rt-lts and with rebasing v6.18.13-rt4-rebase [3] onto v6.18.39 (and
later on applying our own distribution patches) [4], we run into a build failure
though.
(The rebase applied cleanly).

```
  CC [M]  drivers/misc/cardreader/rts5249.o
drivers/tty/serial/8250/8250_port.c:3225:7: error: conflicting types for ‘serial8250_fifo_wait_for_lsr_thre’; have ‘void(struct uart_8250_port *, struct nbcon_write_context *, unsigned int)’
 3225 |  void serial8250_fifo_wait_for_lsr_thre(struct uart_8250_port *up,
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/tty/serial/8250/8250_port.c:40:
drivers/tty/serial/8250/8250.h:189:6: note: previous declaration of ‘serial8250_fifo_wait_for_lsr_thre’ with type ‘void(struct uart_8250_port *, unsigned int)’
  189 | void serial8250_fifo_wait_for_lsr_thre(struct uart_8250_port *up, unsigned int count);
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ./include/linux/linkage.h:7,
                 from ./include/linux/printk.h:8,
                 from ./include/asm-generic/bug.h:22,
                 from ./arch/x86/include/asm/bug.h:108,
                 from ./arch/x86/include/asm/alternative.h:9,
                 from ./arch/x86/include/asm/barrier.h:5,
                 from ./include/linux/list.h:11,
                 from ./include/linux/module.h:12,
                 from drivers/tty/serial/8250/8250_port.c:14:
drivers/tty/serial/8250/8250_port.c:3245:22: error: conflicting types for ‘serial8250_fifo_wait_for_lsr_thre’; have ‘void(struct uart_8250_port *, struct nbcon_write_context *, unsigned int)’
 3245 | EXPORT_SYMBOL_NS_GPL(serial8250_fifo_wait_for_lsr_thre, "SERIAL_8250");
      |                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./include/linux/export.h:76:28: note: in definition of macro ‘__EXPORT_SYMBOL’
   76 |         extern typeof(sym) sym;                                 \
      |                            ^~~
drivers/tty/serial/8250/8250_port.c:3245:1: note: in expansion of macro ‘EXPORT_SYMBOL_NS_GPL’
 3245 | EXPORT_SYMBOL_NS_GPL(serial8250_fifo_wait_for_lsr_thre, "SERIAL_8250");
      | ^~~~~~~~~~~~~~~~~~~~
drivers/tty/serial/8250/8250.h:189:6: note: previous declaration of ‘serial8250_fifo_wait_for_lsr_thre’ with type ‘void(struct uart_8250_port *, unsigned int)’
  189 | void serial8250_fifo_wait_for_lsr_thre(struct uart_8250_port *up, unsigned int count);
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[6]: *** [scripts/Makefile.build:287: drivers/tty/serial/8250/8250_port.o] Error 1
make[5]: *** [scripts/Makefile.build:544: drivers/tty/serial/8250] Error 2
make[4]: *** [scripts/Makefile.build:544: drivers/tty/serial] Error 2
make[3]: *** [scripts/Makefile.build:544: drivers/tty] Error 2
make[3]: *** Waiting for unfinished jobs....
```

The culprit appears to be this commit:
'Reapply "serial: 8250: Switch to nbcon console"' [5]

I'm not sure who is currently working on the patchset for the 6.18 LTS branch,
but I guess it is worth exploring to drop/adjust the commit and release a new
patchset?
Is the patch still needed?

Best,
David

[1] https://archlinux.org/packages/extra/x86_64/linux-rt/
[2] https://archlinux.org/packages/extra/x86_64/linux-rt-lts/
[3] https://gitlab.archlinux.org/archlinux/packaging/upstream/linux-rt-lts/-/commits/v6.18.13-rt4-rebase
[4] https://gitlab.archlinux.org/archlinux/packaging/upstream/linux-rt-lts/-/commits/v6.18.39-rt4-arch1
[5] https://gitlab.archlinux.org/archlinux/packaging/upstream/linux-rt-lts/-/commit/c5661d54576a9bf12c2fd0eaa2a54baf48e45d4a
[6] https://wiki.linuxfoundation.org/realtime/start

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: Issues building RT patchset v6.18.13-rt4-rebase on top of v6.18.39

[Sebastian Andrzej Siewior]

On 2026-07-20 10:14:02 [+0200], David Runge wrote:
> Hi,
Hi,

> I'm not sure who is currently working on the patchset for the 6.18 LTS branch,
> but I guess it is worth exploring to drop/adjust the commit and release a new
> patchset?
> Is the patch still needed?

It is there
   https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/log/?h=linux-6.18.y-rt
   https://www.kernel.org/pub/linux/kernel/projects/rt/6.18/patches-6.18.37-rt6.tar.xz

the problem is probably that it is not in the stable tree…

> Best,
> David

Sebastian

Re: Issues building RT patchset v6.18.13-rt4-rebase on top of v6.18.39

[David Runge]

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

On 2026-07-20 14:58:05 (+0200), Sebastian Andrzej Siewior wrote:
> It is there
>    https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/log/?h=linux-6.18.y-rt
>    https://www.kernel.org/pub/linux/kernel/projects/rt/6.18/patches-6.18.37-rt6.tar.xz
> 
> the problem is probably that it is not in the stable tree…

Hi Sebastian,

thanks for pointing me to the custom source tarballs and the relevant data in
the linux-rt-devel repository.

To understand this better: Is the 6.18 release series (and future release series
from then on) going to be developed in the linux-rt-devel repository, not the
linux-stable-rt repository?
As downstream package maintainer I am currently relying on the relevant git tags
to be available.

The linux-rt-devel repository seems to cover all new versions, but
linux-stable-rt appears to lack behind the upstream advertised LTS release
series.

In general, I would very much welcome a single repository, instead of the
current situation with two repositories, in case that is feasible for you.
Is there policy around when a specific release series is used in which
repository?

Best,
David

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: Issues building RT patchset v6.18.13-rt4-rebase on top of v6.18.39

[Sebastian Andrzej Siewior]

On 2026-07-21 11:10:02 [+0200], David Runge wrote:
> On 2026-07-20 14:58:05 (+0200), Sebastian Andrzej Siewior wrote:
> > It is there
> >    https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/log/?h=linux-6.18.y-rt
> >    https://www.kernel.org/pub/linux/kernel/projects/rt/6.18/patches-6.18.37-rt6.tar.xz
> > 
> > the problem is probably that it is not in the stable tree…
> 
> Hi Sebastian,
Hi,

> thanks for pointing me to the custom source tarballs and the relevant data in
> the linux-rt-devel repository.
> 
> To understand this better: Is the 6.18 release series (and future release series
> from then on) going to be developed in the linux-rt-devel repository, not the
> linux-stable-rt repository?
> As downstream package maintainer I am currently relying on the relevant git tags
> to be available.

That is somehow odd. I just pushed to the stable-rt repository.

> The linux-rt-devel repository seems to cover all new versions, but
> linux-stable-rt appears to lack behind the upstream advertised LTS release
> series.
> 
> In general, I would very much welcome a single repository, instead of the
> current situation with two repositories, in case that is feasible for you.
> Is there policy around when a specific release series is used in which
> repository?

This should have been handed over but it did not happen. So it remained
in this state. I'm sorry.

I will try to update it once it clashes or needs attention otherwise.
Feel free to ping should I fall behind.

> Best,
> David

Sebastian