From: Vagrant Cascadian <vagrant@debian.org>
To: Marius Bakke <mbakke@fastmail.com>, 40190@debbugs.gnu.org
Cc: Mark H Weaver <mhw@netris.org>
Subject: [bug#40190] Linux-Libre 5.6
Date: Fri, 03 Apr 2020 16:28:07 -0700 [thread overview]
Message-ID: <877dywno8o.fsf@ponder> (raw)
In-Reply-To: <87tv24mnbo.fsf@ponder>
[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]
On 2020-03-31, Vagrant Cascadian wrote:
> On 2020-03-31, Marius Bakke wrote:
>> Vagrant Cascadian <vagrant@debian.org> writes:
>>
>>> On 2020-03-30, Vagrant Cascadian wrote:
>>>> And the second patch, switching to 5.5...
>>>
>>> And a third, rougher, less well tested patch switching to 5.6... which
>>> could obviously be squashed into the previous patches and maybe skip 5.5
>>> altogether.
>>
>> 5.5 is not an LTS kernel, so going straight to 5.6 sounds like the
>> right thing to do. However...
>>
>>> diff --git a/gnu/packages/aux-files/linux-libre/5.5-arm.conf b/gnu/packages/aux-files/linux-libre/5.6-arm.conf
>>> similarity index 100%
>>> rename from gnu/packages/aux-files/linux-libre/5.5-arm.conf
>>> rename to gnu/packages/aux-files/linux-libre/5.6-arm.conf
...
>>
>> This does not seem right. Surely there are _some_ configuration changes
>> in 5.6?
>
> Hence the "rough" patch.
>
> I honestly don't feel solid on all the configuration changes that need
> to happen, so haven't been particularly thorough on auditing those.
>
> Running through "make oldconfig" prompted me with many options about
> things I didn't really have a good grasp of, so the 5.5 changes at
> essentially just the 5.4*.conf copied to 5.5*.conf, and applying the
> copying the resulting .config from building the kernel into git...
>
> I could do the same for 5.6 again blindly taking the new defaults... or
> if someone could help with auditing the config updates, that would be
> great!
I pushed linux-libre 5.6 to master *without* setting it as the default
linux-libre version; only added linux-libre-arm64-generic-5.6 and
linux-libre-arm-generic-5.6 based on it.
Attached are the remaining patches to switch it to the default.
I still haven't thoroughly audited the config changes; this simply
copies 5.4-*.conf to 5.6-*.conf in the first patch, and in the second
patch updates them to 5.6 produced by building the package.
By splitting it into two patches, this allows diffing from the old 5.4
configs, but should maybe be squashed if this gets pushed to master.
Thanks for your review!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-04-03 23:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k13gqhrw.fsf@ponder>
[not found] ` <87sgi0le3g.fsf@ponder>
2020-03-23 4:08 ` [bug#40190] Linux-Libre 5.5.x Vagrant Cascadian
2020-03-30 17:32 ` Vagrant Cascadian
2020-03-30 17:34 ` Vagrant Cascadian
2020-03-31 0:10 ` [bug#40190] Linux-Libre 5.6 Vagrant Cascadian
2020-03-31 14:30 ` Marius Bakke
2020-03-31 17:44 ` Vagrant Cascadian
2020-03-31 18:35 ` Guillaume Le Vaillant
2020-04-03 23:28 ` Vagrant Cascadian [this message]
2020-04-03 23:29 ` Vagrant Cascadian
2020-04-16 19:37 ` Vagrant Cascadian
2020-04-17 19:26 ` Mark H Weaver
2020-06-08 20:46 ` [bug#40190] Linux-Libre 5.7 Vagrant Cascadian
2020-06-09 2:43 ` [bug#40190] Linux-Libre 5.6 Leo Famulari
2020-04-06 4:12 ` [bug#40190] Works for me Brendan Tildesley
2020-04-06 10:38 ` [bug#40190] v4l2loopback module builds with 5.4 but not 5.6 Brendan Tildesley
2020-04-06 10:46 ` Danny Milosavljevic
2020-04-06 11:01 ` Tobias Geerinckx-Rice via Guix-patches via
2020-08-05 21:29 ` bug#40190: Linux-Libre 5.5.x Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dywno8o.fsf@ponder \
--to=vagrant@debian.org \
--cc=40190@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).