From: Jan Kiszka <jan.kiszka@web.de>
To: Pavel Machek <pavel@denx.de>, Ulrich Hecht <uli@fpond.eu>
Cc: cip-dev <cip-dev@lists.cip-project.org>
Subject: 4.4 localversion-st
Date: Tue, 2 May 2023 15:37:20 +0200 [thread overview]
Message-ID: <2bf16d2e-7c8d-467f-2f72-3e0925536dbb@web.de> (raw)
Hi all,
I just noticed in some error message that our 4.4 kernels are reporting
themselves as "4.4.302-cip74-st39", and that extra -st39 is coming from
localversion-st. Is that intentional or an accidental effect of merging
the -st tree into the cip branch?
Jan
next reply other threads:[~2023-05-02 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 13:37 Jan Kiszka [this message]
2023-05-03 18:02 ` 4.4 localversion-st Pavel Machek
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=2bf16d2e-7c8d-467f-2f72-3e0925536dbb@web.de \
--to=jan.kiszka@web.de \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@denx.de \
--cc=uli@fpond.eu \
/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