From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] kernel: update to 4.14.212
Date: Wed, 16 Dec 2020 09:58:25 +0100 [thread overview]
Message-ID: <062AD88A-D419-4593-8864-A457C4C17134@ipfire.org> (raw)
In-Reply-To: <20201216063357.19431-1-arne_f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
Hello Arne,
Thank you for submitting this patch, but what am I supposed to do with it?
Are there any urgent fixes in it, so that we have to ship another kernel in the next Core Update again?
I would like to avoid this at all costs, because we are simply not able to test any kernels at the moment because of the pace they are showing up in the build system - and I would rather spend my time on testing 5.10.
Best,
-Michael
> On 16 Dec 2020, at 07:33, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>
> Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
> ---
> lfs/linux | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/linux b/lfs/linux
> index e4467c477..5abc6f93a 100644
> --- a/lfs/linux
> +++ b/lfs/linux
> @@ -24,8 +24,8 @@
>
> include Config
>
> -VER = 4.14.211
> -ARM_PATCHES = 4.14.211-ipfire0
> +VER = 4.14.212
> +ARM_PATCHES = 4.14.212-ipfire0
>
> THISAPP = linux-$(VER)
> DL_FILE = linux-$(VER).tar.xz
> @@ -79,7 +79,7 @@ objects =$(DL_FILE) \
> $(DL_FILE) = $(URL_IPFIRE)/$(DL_FILE)
> arm-multi-patches-$(ARM_PATCHES).patch.xz = $(URL_IPFIRE)/arm-multi-patches-$(ARM_PATCHES).patch.xz
>
> -$(DL_FILE)_MD5 = 41241e9508acc9183540db785f78ec78
> +$(DL_FILE)_MD5 = 645d5256adf72569e14edcf80c3757dc
> arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = 2b0e8e3ebe9827b2bfed7397b043dbc5
>
> install : $(TARGET)
> --
> 2.17.1
>
prev parent reply other threads:[~2020-12-16 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 6:33 Arne Fitzenreiter
2020-12-16 8:58 ` 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=062AD88A-D419-4593-8864-A457C4C17134@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