From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] kernel: update to 4.14.230
Date: Mon, 12 Apr 2021 20:01:36 +0200 [thread overview]
Message-ID: <965a9f93-4974-8ad2-e6b2-ed8482ddf13d@ipfire.org> (raw)
In-Reply-To: <FAB42597-234F-4819-AC42-CC01CFE52E25@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2907 bytes --]
Hello Michael, hello Arne, hello *,
I guess Arne just had this kernel version at hands - thank you, Arne. :-)
To put an end to this topic: Unless something really, really, really terrible happens (looking at you, Intel!),
I propose to stay with Linux 4.14.230 for Core Update 157 then, and make this our last release of the 4.14.x
series. Looking forward to kernel 5.10.x ... :-)
Thanks, and best regards,
Peter Müller
> Hello,
>
> What is the rationale for this patch with reference to this:
>
> https://lists.ipfire.org/pipermail/development/2021-April/009913.html
>
> -Michael
>
>> On 11 Apr 2021, at 20:38, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>>
>> Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
>> ---
>> config/kernel/kernel.config.x86_64-ipfire | 2 +-
>> lfs/linux | 8 ++++----
>> 2 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
>> index 65c365c1b..c15fa8efc 100644
>> --- a/config/kernel/kernel.config.x86_64-ipfire
>> +++ b/config/kernel/kernel.config.x86_64-ipfire
>> @@ -1,6 +1,6 @@
>> #
>> # Automatically generated file; DO NOT EDIT.
>> -# Linux/x86 4.14.229 Kernel Configuration
>> +# Linux/x86 4.14.230 Kernel Configuration
>> #
>> CONFIG_64BIT=y
>> CONFIG_X86_64=y
>> diff --git a/lfs/linux b/lfs/linux
>> index 86acc14f7..e6030bd49 100644
>> --- a/lfs/linux
>> +++ b/lfs/linux
>> @@ -1,7 +1,7 @@
>> ###############################################################################
>> # #
>> # IPFire.org - A linux based firewall #
>> -# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
>> +# Copyright (C) 2007-2021 IPFire Team <info(a)ipfire.org> #
>> # #
>> # This program is free software: you can redistribute it and/or modify #
>> # it under the terms of the GNU General Public License as published by #
>> @@ -24,8 +24,8 @@
>>
>> include Config
>>
>> -VER = 4.14.229
>> -ARM_PATCHES = 4.14.229-ipfire0
>> +VER = 4.14.230
>> +ARM_PATCHES = 4.14.230-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 = 9d4cf6e9ffff893d8a2ecea6a8c5a15b
>> +$(DL_FILE)_MD5 = 9fceffba37032235767745a83b2f7ad2
>> arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = a04b842733999abb818cabb0388572b8
>>
>> install : $(TARGET)
>> --
>> 2.25.1
>>
>
prev parent reply other threads:[~2021-04-12 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 19:38 Arne Fitzenreiter
2021-04-12 8:59 ` Michael Tremer
2021-04-12 18:01 ` Peter Müller [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=965a9f93-4974-8ad2-e6b2-ed8482ddf13d@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