From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Should we go for Linux 5.15.64 for Core Update 170?
Date: Fri, 02 Sep 2022 16:45:33 +0000 [thread overview]
Message-ID: <d7ab437f-7b14-b9eb-3301-aaafbb38a345@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Hello development folks,
earlier today, I came across https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.64, in
which several commits caught my attention, particularly all those in the tcp/netfilter subsystems.
Generally, I am not a fan of updating the kernel in Core Updates while they are already in
testing (unless something is badly broken, of course), since this is an uphill battle, and in
the past has delayed releases quite notably.
Therefore, I would be grateful for input, since I am not too sure how to judge the severity of
these aforementioned kernel commits. Is this something we should bring to our users sooner rather
than later? Does anything strike you as "hey, we have dealt with this bug for ages, and it is
finally resolved upstream"?
Thanks in advance, and best regards,
Peter Müller
next reply other threads:[~2022-09-02 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 16:45 Peter Müller [this message]
2022-09-05 9:59 ` Michael Tremer
2022-09-05 10:53 ` Adolf Belka
2022-09-08 10:20 ` 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=d7ab437f-7b14-b9eb-3301-aaafbb38a345@ipfire.org \
--to=peter.mueller@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