Hello, On Wed, May 14, 2025 at 08:56:01AM +0200, Geert Uytterhoeven wrote: > On Tue, 13 May 2025 at 22:19, "Uwe Kleine-König" <ukleinek@xxxxxxxxxx> wrote: > > The obvious options are (in order of my preference): > > > > - Geert declares his renesas-arm-defconfig-for-v6.16 to be stable and I > > merge it into my tree and then apply the patch > > - I cherry pick 5ad7de623853 in my pwm tree and Geert drops it > > - I delay applying the patch until after v6.16-rc1 > > > > Geert: What is your preference? Let's discuss on irc? > > My tag renesas-arm-defconfig-for-v6.16-tag2 is stable, as that is > already merged in the soc tree. > > However, renaming config symbols always comes with its own set of > pains: users must notice and adapt when updating their own configs, > and I do have to manage the non-upstream renesas_defconfig, too. > What about dropping the rename part? The symbols that currently lack > a RENESAS-prefix do have fairly unique family prefixes. > > Morimoto-san: Would that still be OK for you? I agreed with Geert off-list that merging renesas-arm-defconfig-for-v6.16-tag2 into the pwm tree and apply the patch is fine for him. That's what I did now. Thanks Uwe
Attachment:
signature.asc
Description: PGP signature
