[PATCH] gemini: Bump to kernel v5.10

[Christian Lamparter]

Hello,

On 15/04/2021 01:51, Linus Walleij wrote:
> On Tue, Apr 13, 2021 at 11:37 PM Hauke Mehrtens <hauke at hauke-m.de> wrote:
> 
>> The target kernel configurations should be small and most of the generic
>> settings should be done in the target/linux/generic/config-* config file.
>> The target configuration only contains the extra configuration options
>> or the options which are different.
> (...)
>> You can add new generic options to target/linux/generic/config-5.10
>> manually.
> 
> OK I get it, I sent a slew of patches to the generic config.
> 
> We drive-by contributors just assume the generic config is
> Perfect(TM) you know, now I realize I have to contribute to that
> effort.
> 

That was nicely worded... Yeah I know, there's no need for this.
In my case: That CoVID workload has bogged me down during the week.
I sometimes have a bit of spare-time on the weekends.

 From what I can tell, the situation is: your gemini target would
be the first target that isn't "source-only" (which means it gets
skipped by the builderbots) that likes to fully switch to 5.10.
So you'll get all the fun of having to endure broken packages,
or have to come up with fixes for other stuff to make the buildbot
happy.

This might look overly cautions, but when I foolishly "merged" my
apm82181 testing 5.10 I broke other targets 5.10 support so bad
that the "fix patch" needed a second "fix patch". :(

And as you have seen even something as simple as a default for
a CONFIG_* SYMBOL can a show-stopper due deer-in-the-headlights
moments from crucial dependencies in different packages like musl...

>> For example do you really need CONFIG_OABI_COMPAT for gemini?
>>
>> You should try to remove just most of the options which are not SoC
>> specific.
> 
> Yups I managed to diet out a bunch of stuff.
> 

Do you have an update? I've queued your patch with "one weird trick"
(use KERNEL_TESTING_PATCHVER instead of KERNEL_PATCHVER).
<https://git.openwrt.org/?p=openwrt/staging/chunkeey.git;a=commit;h=a257f9b2bb6857760aa64ac1a8112853e382272e>

Yes, this will cause the buildbot to still built your target with 5.4
but the 5.10 support will be there (behind CONFIG_TESTING_KERNEL).

Cheers,
Christian