Re: Dealing with SUBLEVEL overflow in backports

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2022-02-07 at 11:09 +0000, Jiaxun Yang wrote:
> 
> 在 2022/2/7 10:50, Johannes Berg 写道:
> > On Mon, 2022-02-07 at 10:15 +0100, Johannes Berg wrote:
> > > On Mon, 2022-02-07 at 01:19 +0000, Jiaxun Yang wrote:
> > > > Hi backport forks,
> > > > 
> > > > I was trying to fix ckmake FAIL building against 4.9 for 4.9.297+.
> > > > 
> > > > I found that macro KERNEL_VERSION_IN_RANGE(4,9,297, 4,10,0) won't work
> > > > because SUBLEVEL 297 had overflowed 4 bit (255) in KERNEL_VERSION.
> > > > 
> > > > How are we supposed to deal with such situation?
> > > > 
> > > Hm. I guess the only way would be to somehow make a Kconfig variable in
> > > backports, that uses the Makefile settings? But env="SUBLEVEL" doesn't
> > > work, so not sure, maybe some Makefile trickery to extract it and write
> > > it to the config?

> Or is it possible to persuade stable forks to define LINUX_VERSION_SUBLEVEL
> on existing stable releases?

Probably not.

> > > 
> > Or just find a way to handle the specific area? Is this for the
> > build_bug.h stuff?

> Yes, any idea?
> 

Looking at commit b29eec6c49, does it even matter? We can continue using
bug.h which includes build_bug.h, it's just pulling in more than needed.

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



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux