all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Mark H Weaver <mhw@netris.org>
Cc: Marius Bakke <mbakke@fastmail.com>, 40190@debbugs.gnu.org
Subject: [bug#40190] Linux-Libre 5.6
Date: Thu, 16 Apr 2020 12:37:31 -0700	[thread overview]
Message-ID: <87imhzb4sk.fsf@yucca> (raw)
In-Reply-To: <874ku0no5n.fsf@ponder>

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

On 2020-04-03, Vagrant Cascadian wrote:
> On 2020-04-03, Vagrant Cascadian wrote:
>> Attached are the remaining patches to switch it to the default.
>
> At least, it is attached now...

Ping?

I think the patcset now needs some minor updates to apply to master, but
just wondering when we could consider switching to 5.6... ?


live well,
  vagrant

> From c0200684371c8126b5b6579c16f8d71aa19ea44c Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <vagrant@debian.org>
> Date: Fri, 3 Apr 2020 22:08:50 +0000
> Subject: [PATCH 1/2] gnu: linux-libre: Update to 5.6.
>
> * gnu/packages/linux (linux-libre-version, linux-libre-pristine-source,
>   linux-libre-source, linux-libre): Update to 5.6.
>   (linux-libre-arm-generic-5.4, linux-libre-arm-omap2plus-5.4,
>   linux-libre-arm64-generic-5.4, linux-libre-riscv64-generic-5.4,
>   linux-libre-arm64-generic-5.4): New variables.
>   (linux-libre-arm-generic-5.6, linux-libre-arm64-generic-5.6): Remove
>   obsolete variables.
> * gnu/packages/aux-files/linux-libre/5.6-arm.conf: New file.
> * gnu/packages/aux-files/linux-libre/5.6-arm64.conf: New file.
> * gnu/packages/aux-files/linux-libre/5.6-i686.conf: New file.
> * gnu/packages/aux-files/linux-libre/5.6-x86_64.conf: New file.
> * Makefile.am (AUX_FILES): Update accordingly.

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

  reply	other threads:[~2020-04-16 19:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 19:14 RFC: Linux-Libre 5.5.x on pinebook pro Vagrant Cascadian
2020-03-19 19:25 ` Vincent Legoll
2020-03-20  4:35   ` Vagrant Cascadian
2020-03-22 13:21 ` RFC: Linux-Libre 5.5.x Vagrant Cascadian
2020-03-23  4:08   ` Vagrant Cascadian
2020-03-23  4:08     ` [bug#40190] " 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
2020-04-03 23:29                 ` Vagrant Cascadian
2020-04-16 19:37                   ` Vagrant Cascadian [this message]
2020-04-17 19:26                     ` Mark H Weaver
2020-06-08 20:46                       ` [bug#40190] Linux-Libre 5.7 Vagrant Cascadian
2020-06-08 20:52                         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87imhzb4sk.fsf@yucca \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.