Re: Dealing with SUBLEVEL overflow in backports

Hauke Mehrtens <[email protected]> Thu, 10 Feb 2022 00:45:39 +0100
Newsgroups org.kernel.vger.backports
Message-ID <[email protected]>
On 2/10/22 00:44, Hauke Mehrtens wrote:
> On 2/8/22 16:51, Jiaxun Yang wrote:
>>
>>
>> 在 2022/2/8 15:02, Johannes Berg 写道:
>>> On Tue, 2022-02-08 at 14:50 +0000, Jiaxun Yang wrote:
>>>> Ah I tried this approach but find that this may break other modules
>>>> depending on our headers because the cflag won't come with be
>>>> inherited by them.
>>>>
>>> Hm. I thought about if that could happen, but decided not? We only
>>> compile C files in backports, which other parts would break?
>>
>> For example OpenWRT compiles mac80211 purely from backports.
>>
>> So for other out-of-tree wireless drivers they have to include headers
>> provided by backports, but they can't recieve cflags from our makefile.
>>
>> So it will leave those macros undefined ad led to problems.
>>
>> Thanks.
>> - Jiaxun
>>
>>>
>>> johannes
>>
> Hi,
> 
> What build problem do you get when you include "#include <linux/bug.h>" 
> here on kernel 4.9.299? Can we somehow work around this problem by 
> detection the kernel version in a different way based on a different 
> define?
> 
> Hauke

OpenWrt does not use kernel 4.9 any more, we could also drop the support 
for some external modules using backports on such old kernel versions.

Hauke
--
To unsubscribe from this list: send the line "unsubscribe backports" in