From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: kernel: update to 6.1.x
Date: Mon, 09 Jan 2023 15:33:35 +0000 [thread overview]
Message-ID: <40B356FD-2785-4917-AACB-6ECFCE93B7A4@ipfire.org> (raw)
In-Reply-To: <20230107114701.4075482-1-arne_f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
Hello Arne,
Thank you very much for this patchset. A new kernel!
Is this supposed to be included in the coming Core Update where we planned to ship a kernel anyways, or do you feel that this major update will need some more testing?
I don’t believe that we are in any kind of rush at the moment to have the next update released, so it would feel okay for me to include it in 173.
Best,
-Michael
> On 7 Jan 2023, at 11:46, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>
> this series update the kernel to 6.1.3 and also some other needed
> updates.
>
>
prev parent reply other threads:[~2023-01-09 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 11:46 Arne Fitzenreiter
2023-01-07 11:46 ` [PATCH 1/9] postfix: patch for build with kernel 6.x Arne Fitzenreiter
2023-01-07 11:46 ` [PATCH 2/9] rtl8189es: update to e58bd86c9d9408c648b1246a0dd76b16856ec172 Arne Fitzenreiter
2023-01-07 11:46 ` [PATCH 3/9] rtl8189fs: update to 476020109b3841421af289a7b78c7a25b0c45fac Arne Fitzenreiter
2023-01-07 11:46 ` [PATCH 4/9] rtl8822bu: update to 20210702-2590672d717e2516dd2e96ed66f1037a6815bced Arne Fitzenreiter
2023-01-07 11:46 ` [PATCH 5/9] rtl8812au: update to 20210629-07ac856293e247347b891c5dbd13f3ab8321132d Arne Fitzenreiter
2023-01-07 11:46 ` [PATCH 6/9] rtl8821cu: update to 20210118-7b8c45a270454f05e2dbf3beeb4afcf817db65da Arne Fitzenreiter
2023-01-07 11:46 ` [PATCH 7/9] strace: update to 6.1 Arne Fitzenreiter
2023-01-07 11:47 ` [PATCH 8/9] xradio: disabled build Arne Fitzenreiter
2023-01-09 15:33 ` Michael Tremer [this message]
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=40B356FD-2785-4917-AACB-6ECFCE93B7A4@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