From: Hauke Mehrtens <hauke@hauke-m.de>
To: Johannes Berg <johannes@sipsolutions.net>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
backports@vger.kernel.org
Subject: Re: Dealing with SUBLEVEL overflow in backports
Date: Mon, 7 Feb 2022 23:18:21 +0100 [thread overview]
Message-ID: <9886de4b-7e5c-ee34-6e2c-83efb358d1ac@hauke-m.de> (raw)
In-Reply-To: <f234795fbc9ba700982d5182f3cb71d5a0408c17.camel@sipsolutions.net>
On 2/7/22 14:57, Johannes Berg wrote:
> On Mon, 2022-02-07 at 13:40 +0000, Jiaxun Yang wrote:
>>
>> Sorry I didn't follow, the problem for 4.9.297+ is when we are including
>> bug.h, it just include build_bug.h from backport-include.
>> Then in backport-include build_bug.h, the include_next is excluded so
>> the real build_bug.h from kernel tree is never included and thus those
>> macros supposed to be in build_bug.h can never work.
>>
>
> Ah! Now I understand. Hmm, don't think I have a solution off the top of
> my head ...
>
> johannes
Hi,
The LINUX_VERSION_CODE is fixed since 4.9.255, see here:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=42efb098c75f9d4b95f7cf35d3d52e80cc2fde82
SUBLEVEL should still contains the minor kernel version number.
We could extend the macros in backport/backport-include/linux/version.h
to check for SUBLEVEL manually if it overflows.
Hauke
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2022-02-07 22:18 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
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 [this message]
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=9886de4b-7e5c-ee34-6e2c-83efb358d1ac@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=johannes@sipsolutions.net \
/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.