unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Vagrant Cascadian <vagrant@debian.org>, 40190@debbugs.gnu.org
Cc: Mark H Weaver <mhw@netris.org>
Subject: [bug#40190] Linux-Libre 5.6
Date: Tue, 31 Mar 2020 16:30:05 +0200	[thread overview]
Message-ID: <87369ovbpu.fsf@devup.no> (raw)
In-Reply-To: <874ku5fkoq.fsf@ponder>

[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]

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
> diff --git a/gnu/packages/aux-files/linux-libre/5.5-arm64.conf b/gnu/packages/aux-files/linux-libre/5.6-arm64.conf
> similarity index 100%
> rename from gnu/packages/aux-files/linux-libre/5.5-arm64.conf
> rename to gnu/packages/aux-files/linux-libre/5.6-arm64.conf
> diff --git a/gnu/packages/aux-files/linux-libre/5.5-i686.conf b/gnu/packages/aux-files/linux-libre/5.6-i686.conf
> similarity index 100%
> rename from gnu/packages/aux-files/linux-libre/5.5-i686.conf
> rename to gnu/packages/aux-files/linux-libre/5.6-i686.conf
> diff --git a/gnu/packages/aux-files/linux-libre/5.5-x86_64.conf b/gnu/packages/aux-files/linux-libre/5.6-x86_64.conf
> similarity index 100%
> rename from gnu/packages/aux-files/linux-libre/5.5-x86_64.conf
> rename to gnu/packages/aux-files/linux-libre/5.6-x86_64.conf

This does not seem right.  Surely there are _some_ configuration changes
in 5.6?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-03-31 14:31 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 [this message]
2020-03-31 17:44             ` Vagrant Cascadian
2020-03-31 18:35               ` Guillaume Le Vaillant
2020-04-03 23:28               ` Vagrant Cascadian
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=87369ovbpu.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=40190@debbugs.gnu.org \
    --cc=mhw@netris.org \
    --cc=vagrant@debian.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).