From: Jari Ruusu <jariruusu@protonmail.com> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Sasha Levin <sashal@kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "stable@vger.kernel.org" <stable@vger.kernel.org> Subject: Kernel version numbers after 4.9.255 and 4.4.255 Date: Thu, 04 Feb 2021 05:59:42 +0000 Message-ID: <7pR0YCctzN9phpuEChlL7_SS6auHOM80bZBcGBTZPuMkc6XjKw7HUXf9vZUPi-IaV2gTtsRVXgywQbja8xpzjGRDGWJsVYSGQN5sNuX1yaQ=@protonmail.com> (raw) Greg, I hope that your linux kernel release scripts are implemented in a way that understands that PATCHLEVEL= and SUBLEVEL= numbers in top-level linux Makefile are encoded as 8-bit numbers for LINUX_VERSION_CODE and KERNEL_VERSION() macros, and must stay in range 0...255. These 8-bit limits are hardcoded in both kernel source and userspace ABI. After 4.9.255 and 4.4.255, your scripts should be incrementing a number in EXTRAVERSION= in top-level linux Makefile. -- Jari Ruusu 4096R/8132F189 12D6 4C3A DCDA 0AA4 27BD ACDF F073 3C80 8132 F189
next reply index Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-04 5:59 Jari Ruusu [this message] 2021-02-04 6:20 ` Greg Kroah-Hartman 2021-02-04 7:26 ` Jiri Slaby 2021-02-04 8:51 ` Greg Kroah-Hartman 2021-02-04 11:00 ` Jiri Slaby 2021-02-04 16:28 ` David Laight 2021-02-04 16:48 ` Greg Kroah-Hartman 2021-02-04 20:19 ` Christoph Biedl 2021-02-05 6:52 ` Greg KH 2021-02-05 17:31 ` Tony Battersby 2021-02-05 18:11 ` Mauro Carvalho Chehab 2021-02-06 7:20 ` Greg Kroah-Hartman 2021-02-06 9:24 ` Mauro Carvalho Chehab 2021-02-06 9:29 ` Greg Kroah-Hartman 2021-02-06 9:48 ` Mauro Carvalho Chehab 2021-02-06 10:18 ` Hans Verkuil 2021-02-06 11:18 ` Mauro Carvalho Chehab 2021-02-06 7:22 ` Greg Kroah-Hartman 2021-02-05 9:06 ` Pavel Machek 2021-02-05 9:33 ` Greg Kroah-Hartman 2021-02-05 18:44 ` Pavel Machek 2021-02-06 7:23 ` Greg Kroah-Hartman
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='7pR0YCctzN9phpuEChlL7_SS6auHOM80bZBcGBTZPuMkc6XjKw7HUXf9vZUPi-IaV2gTtsRVXgywQbja8xpzjGRDGWJsVYSGQN5sNuX1yaQ=@protonmail.com' \ --to=jariruusu@protonmail.com \ --cc=gregkh@linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=sashal@kernel.org \ --cc=stable@vger.kernel.org \ /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
LKML Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \ linux-kernel@vger.kernel.org public-inbox-index lkml Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git