unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@lists.gnu.org
Cc: Mark H Weaver <mhw@netris.org>,
	Marius Bakke <mbakke@fastmail.com>,
	40190@debbugs.gnu.org
Subject: [bug#40190] Linux-Libre 5.7
Date: Mon, 08 Jun 2020 13:46:03 -0700	[thread overview]
Message-ID: <87o8ptffqs.fsf@ponder> (raw)
In-Reply-To: <87imhxud4b.fsf@netris.org>

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

On 2020-04-17, Mark H Weaver wrote:
> Vagrant Cascadian <vagrant@debian.org> wrote:
>> I think the patcset now needs some minor updates to apply to master, but
>> just wondering when we could consider switching to 5.6... ?
>
> I do not wish to be a blocker on this, and moreover I would welcome it
> if someone else would step up to take over maintenance of our kernel
> packages.

Thanks for all your work!

I've just pushed the source update for 5.7.1 (and packages for
linux-libre-arm*-generic)...


> However, I should say that for all previous kernel upgrades, I have
> taken the time to consider each of the new configuration options
> presented by "make oldconfig" and to try make a sensible choice for each
> one.  I have not found it sufficient to rely on the automatically
> selected choices, which very often default to "no" for modules that
> ought to be included, and occasionally default to "yes" for options that
> are contrary to our commitment to the GNU FSDG.
>
> I will leave it up to the Guix maintainers to decide what to do if no
> one volunteers to take up the job of properly updating our default
> kernel configurations.

I still do not have the the time, ability or confidence to review
updating the configs for multiple architectures...

I wasn't able to produce a working config for 5.7.x on x86_64 (issues
with graphics on intel prevented sway from loading), let alone one that
has been scrutinized for correctness in terms of GNU FSDG.

Can anyone else step in to help with reviewing kernel config updates?

Alternately, is it plausible to work out a blacklist/whitelist feature
for options that can get updated more dynamically that a whole kernel
config? That's well outside my skillset in terms of guile, but that
might be a more maintainable option for the future...


live well,
  vagrant

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

  reply	other threads:[~2020-06-08 20:47 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
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                       ` Vagrant Cascadian [this message]
2020-06-09  2:43                       ` 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=87o8ptffqs.fsf@ponder \
    --to=vagrant@debian.org \
    --cc=40190@debbugs.gnu.org \
    --cc=guix-devel@lists.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).