all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Any objections to removing linux-libre@4.1?
Date: Fri, 09 Jun 2017 12:50:03 -0400	[thread overview]
Message-ID: <87lgp15cn8.fsf@netris.org> (raw)
In-Reply-To: <87y3t2eeh7.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 08 Jun 2017 16:33:24 +0200")

Ricardo Wurmus <rekado@elephly.net> writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> Does anyone here still need linux-libre@4.1 in Guix?  If not, I'd like
>> to remove it.
>
> Is this not the only version of Linux libre that does not expose the
> system clock bug Libreboot users suffer from?

I don't know.  I had a vague recollection of hearing that the problem
has since been resolved, but I'm not sure.

> I’m still using 4.1 on one of my machines for that reason until I can
> upgrade Libreboot.

Okay, we can hold off on removing it for now.  However, Sasha Levin (the
upstream linux-4.1.x maintainer) told me that this series will reach
end-of-life in 2 months, at which point it will stop receiving security
updates.  At that point we'll need to remove 4.1 and find another
solution for Libreboot users, if needed.  One option would be to add a
much older LTS kernel.  Of those, the most well maintained (judging
solely by the dates of their most recent release) seem to be 3.16 and
3.2.

      Mark

      reply	other threads:[~2017-06-09 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04  6:11 Any objections to removing linux-libre@4.1? Mark H Weaver
2017-06-04 16:31 ` Leo Famulari
2017-06-04 19:54   ` Mark H Weaver
2017-06-04 21:47   ` Mark H Weaver
2017-06-05 21:46     ` Leo Famulari
2017-06-06  0:59       ` Mark H Weaver
2017-06-04 21:19 ` Ludovic Courtès
2017-06-08 14:33 ` Ricardo Wurmus
2017-06-09 16:50   ` Mark H Weaver [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=87lgp15cn8.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.