[OpenWrt-Devel] Kernel version for OpenWrt 20.X

Hauke Mehrtens hauke at hauke-m.de
Tue Jan 7 17:09:31 EST 2020


On 1/7/20 12:32 PM, Adrian Schmutzler wrote:
> Hi Hauke,
> 
>> -----Original Message-----
>> From: openwrt-devel [mailto:openwrt-devel-bounces at lists.openwrt.org] On
>> Behalf Of Hauke Mehrtens
>> Sent: Sonntag, 5. Januar 2020 14:54
>> To: mail at adrianschmutzler.de; 'OpenWrt Development List' <openwrt-
>> devel at lists.openwrt.org>
>> Cc: 'Koen Vandeputte' <koen.vandeputte at ncentric.com>
>> Subject: Re: [OpenWrt-Devel] Kernel version for OpenWrt 20.X
>>
>> On 1/5/20 2:43 PM, mail at adrianschmutzler.de wrote:
>>>>>>> On 11/28/19 7:11 PM, Adrian Schmutzler wrote:
>>>>>>>> Hi Hauke,
>>>>>>>>
>>>>>>>>> The following are still on kernel 4.9:
>>>>>>>>>  * ar7
>>>>>>>>>  * ixp4xx
>>>>>>>>>  * orion
>>>>>>>>
>>>>>>>> There are patches (actually from you, May 2019) on the list which
>>>>>>>> claim to bump ar7 and orion to 4.14:
>>>>>>>>
>>>>>>>> https://patchwork.ozlabs.org/project/openwrt/list/?series=107337
>>>>>>>> https://patchwork.ozlabs.org/project/openwrt/list/?series=107339
>>>>>>>>
>>>>>>>> I haven't looked closer, just in case you forgot about them ;-)
>>>>>>>
>>>>>>> Nobody reported that they are working so I never applied them. I do
>>>>>>> not have the hardware, I just made them compile.
>>>>>>
>>>>>> Since there was no response of any kind from a third party, I've
>>>>>> just
>>>>> marked the two patchsets as "Deferred" in the patchwork, so we get a
>>>>> little more overview there. I hope that's okay for you.
>>>>>
>>>>> Yes fine with me, we should probably drop these targets soon.
>>>>>
>>>>> Hauke
>>>>
>>>> I think it's time to remove the three targets and kernel 4.9 support as
>>>> well
>>>> after the release has been made. Or does keeping kernel 4.9 in master
>>>> (even
>>>> without targets) make it easier to support 18.06 branch?
>>
>> No, it does not help me to have kernel 4.9 is master for maintaining 18.06.
>>
>>> I've prepared a staging branch for that (completely untested at the
>>> moment):
>>>
>> https://git.openwrt.org/?p=openwrt/staging/adrian.git;a=shortlog;h=refs/heads
>> /remove49
>>
>> Thank you.
>>
>> Before applying this please send this to the public mailing list.
>>
>>> For orion, I have some grep matches in uboot-kirkwood and
>>> kernel/linux/modules/usb.mk I'm not sure about, so I haven't touched those
>>> yet.
>>
>> The orion part in usb.mk is also used by mvebu:
>> https://cateee.net/lkddb/web-lkddb/USB_EHCI_HCD_ORION.html
>>
>> uboot-kirkwood probably also uses some orion parts in the kirkwood target.
>>
>> I think kmod-crypto-iv is empty now.
>>
>> There are also some checks in include/netfilter.mk which can be removed now.
>>
>> This file can also be removed:
>> package/kernel/linux/files/sysctl-tcp-bbr-k4_9.conf
>>
>>
>> Hauke
> 
> If we remove the targets anyway, I wonder whether we shouldn't add your two 4.14 patchsets to master directly beforehand.
> That way, we would have them in master history, where they would be easier to find for someone wanting to use the target for whatever reason. (I'd add an explanation of the situation to the commit message.) Still, having removed the target afterwards, no harm would be caused by the patches being untested. This would preserve your work there to someone looking for it, while not affecting working master in any way and without much additional work.
> 
> What do you think?

Sounds good.

I do not think they will be added again because the hardware is very
only now.

Hauke

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20200107/d2cd44f1/attachment.sig>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


More information about the openwrt-devel mailing list