Bug#1053503: Enable support for Renesas RZ/V2L, RZ/G2UL, and RZ/V2M

From	Salvatore Bonaccorso <carnil@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#1053503: Enable support for Renesas RZ/V2L, RZ/G2UL, and RZ/V2M
Date	2023-11-04 10:10 +0100
Message-ID	<HwkPf-32fC-1@gated-at.bofh.it> (permalink)
References	<HlswN-dGnl-1@gated-at.bofh.it> <Hw4U9-2S5i-1@gated-at.bofh.it> <HlswN-dGnl-1@gated-at.bofh.it> <Hw4U9-2S5i-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

Hi,

On Fri, Nov 03, 2023 at 05:08:49PM +0100, Emanuele Rocca wrote:
> Hi!
> 
> On 2023-10-05 10:05, John wrote:
> > CONFIG_ARCH_R9A07G054=y
> > CONFIG_ARCH_R9A07G043=y
> > CONFIG_ARCH_R9A09G011=y
> 
> The changes have been merged into master some time ago already:
> https://salsa.debian.org/kernel-team/linux/-/merge_requests/867
> 
> Salvatore: what is the best way to ensure this makes its way into the
> next upload to sid? Should I open a new MR against sid, or can you just
> cherry-pick commit 87656545c ?

I'm not sure this is really that urgent, 6.5.10 will be EOL upstream
at some point and in master branch Bastian et all are prearing the 6.6
based once. After an extra round in experimental I would expect it
will now not take too much longer to have a version including this
change as well in unstable. 

But if it's urgent to have earlier in unstble with the next upload
already then we can cherry-pick the mentioned commit.

Regards,
Salvatore

Thread

Bug#1053503: Enable support for Renesas RZ/V2L, RZ/G2UL, and RZ/V2M Emanuele Rocca <ema@debian.org> - 2023-11-03 17:10 +0100
  Bug#1053503: Enable support for Renesas RZ/V2L, RZ/G2UL, and RZ/V2M Salvatore Bonaccorso <carnil@debian.org> - 2023-11-04 10:10 +0100
    Bug#1053503: Enable support for Renesas RZ/V2L, RZ/G2UL, and RZ/V2M Emanuele Rocca <ema@debian.org> - 2023-11-05 11:20 +0100

csiph-web