From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Fixing our kernel build
Date: Mon, 19 Aug 2024 10:10:46 +0000 [thread overview]
Message-ID: <20240819101048.991691-1-michael.tremer@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Hello everyone,
it has always been a little messy when it comes to the KVER variable.
Depending on when it was used, usually things were appended to it to get
the *actual* kernel release. Chaotic.
Since we now only build one kernel (and probably will be for the near
future) a lot of this is no longer needed and so I consolidated the use
of this variable.
Since the kernel release was put together in an inconsistent way, it was
impossible to build any release candidate kernels because they later got
installed in various places, but not where they were supposed to be.
This is now no longer a problem since there is only one easy way to find
out which kernel we are building for.
This patchset does not introduce any functional changes.
Best,
-Michael
next reply other threads:[~2024-08-19 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 10:10 Michael Tremer [this message]
2024-08-19 10:10 ` [PATCH 2/2] linux: Don't reset CFLAGS/CXXFLAGS Michael Tremer
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=20240819101048.991691-1-michael.tremer@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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
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