From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Julien Olivain <ju.o@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 1/1] package/linux-backports: bump version to 5.15.58
Date: Mon, 15 Aug 2022 11:39:15 +0200 [thread overview]
Message-ID: <20220815113915.33c6816b@windsurf> (raw)
In-Reply-To: <20220814202300.GM2854108@scaer>
On Sun, 14 Aug 2022 22:23:00 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> But then, one could argue that this is the same with other packages that
> get requirements on newer kernel headers (and thus probably about newer
> running kernel). We can't hold back forever.
True. But even systemd only requires 3.13, which is much older than the
minimum 4.4 kernel that would be required by this linux-backports
update.
> The alternate solution is not great: we could add a version choice:
>
> config BR2_PKG_LNX_BACKPORTS_5_15_X
> bool "5.15.x (for kernels back to 4.4)"
>
> config BR2_PKG_LNX_BACKPORTS_5_8_X
> bool "5.8.x (for kernels back to 3.10)"
>
> But this is not ideal... :-/
That is the sort of solution that I was thinking of, indeed.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-15 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 9:36 [Buildroot] [PATCH next 1/1] package/linux-backports: bump version to 5.15.58 Julien Olivain
2022-08-13 10:54 ` Thomas Petazzoni via buildroot
2022-08-13 20:01 ` Julien Olivain
2022-08-14 20:23 ` Yann E. MORIN
2022-08-15 9:39 ` Thomas Petazzoni via buildroot [this message]
2022-08-15 9:52 ` Yann E. MORIN
2022-08-15 20:06 ` Julien Olivain
2022-08-15 9:51 ` Thomas Petazzoni via buildroot
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=20220815113915.33c6816b@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.