From: Johannes Berg <johannes@sipsolutions.net>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>, backports@vger.kernel.org
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: Dealing with SUBLEVEL overflow in backports
Date: Mon, 07 Feb 2022 11:50:19 +0100 [thread overview]
Message-ID: <b372254d9c4cc7156eabfb5dd722d02541a31ea1.camel@sipsolutions.net> (raw)
In-Reply-To: <545f9eb36509c21b3217804b43da4dcdbaf623b1.camel@sipsolutions.net>
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 just find a way to handle the specific area? Is this for the
build_bug.h stuff?
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2022-02-07 10:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 1:19 Dealing with SUBLEVEL overflow in backports Jiaxun Yang
2022-02-07 9:15 ` Johannes Berg
2022-02-07 10:50 ` Johannes Berg [this message]
2022-02-07 11:09 ` Jiaxun Yang
2022-02-07 11:11 ` Johannes Berg
2022-02-07 12:52 ` Jiaxun Yang
2022-02-07 13:04 ` Johannes Berg
2022-02-07 13:40 ` Jiaxun Yang
2022-02-07 13:57 ` Johannes Berg
2022-02-07 22:18 ` Hauke Mehrtens
2022-02-08 7:58 ` Johannes Berg
2022-02-08 14:50 ` Jiaxun Yang
2022-02-08 15:02 ` Johannes Berg
2022-02-08 15:51 ` Jiaxun Yang
2022-02-09 23:44 ` Hauke Mehrtens
2022-02-09 23:45 ` Hauke Mehrtens
2022-02-10 8:17 ` Johannes Berg
2022-02-10 14:05 ` Jiaxun Yang
2022-04-03 23:19 ` Hauke Mehrtens
2022-05-04 12:04 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b372254d9c4cc7156eabfb5dd722d02541a31ea1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=jiaxun.yang@flygoat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.