public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Andreas Helbech Kleist <andreaskleist@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: reatmon@ti.com
Subject: [kirkstone][PATCH 0/3] kernel: Backport v6.3+ localversion fixes
Date: Thu, 22 Feb 2024 11:35:42 +0100	[thread overview]
Message-ID: <20240222103545.2970387-1-andreaskleist@gmail.com> (raw)

Without this, kernels v6.3 and later have wrong localversion '+' appended.

Bruce Ashfield (2):
  kernel: fix localversion in v6.3+
  kernel: make LOCALVERSION consistent between recipes

Ming Liu (1):
  kernel.bbclass: introduce KERNEL_LOCALVERSION

 meta/classes/kernel-arch.bbclass              |  1 -
 meta/classes/kernel.bbclass                   | 24 +++++++++++++++++--
 meta/classes/kernelsrc.bbclass                |  1 +
 meta/classes/linux-kernel-base.bbclass        | 11 +++++++++
 meta/classes/module-base.bbclass              |  1 +
 meta/conf/documentation.conf                  |  1 +
 .../make-mod-scripts/make-mod-scripts_1.0.bb  |  3 +++
 7 files changed, 39 insertions(+), 3 deletions(-)

-- 
2.43.2



             reply	other threads:[~2024-02-22 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 10:35 Andreas Helbech Kleist [this message]
2024-02-22 10:35 ` [kirkstone][PATCH 1/3] kernel.bbclass: introduce KERNEL_LOCALVERSION Andreas Helbech Kleist
2024-02-22 10:35 ` [kirkstone][PATCH 2/3] kernel: fix localversion in v6.3+ Andreas Helbech Kleist
2024-02-22 10:35 ` [kirkstone][PATCH 3/3] kernel: make LOCALVERSION consistent between recipes Andreas Helbech Kleist
2024-02-22 21:51   ` Ryan Eatmon
2024-02-22 21:56     ` [OE-core] " Bruce Ashfield
2024-02-22 22:46       ` Ryan Eatmon
     [not found]       ` <17B650DBED7FC1F0.14827@lists.openembedded.org>
2024-02-23 17:11         ` Ryan Eatmon

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=20240222103545.2970387-1-andreaskleist@gmail.com \
    --to=andreaskleist@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=reatmon@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox