From: Mark H Weaver <mhw@netris.org>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: 22274@debbugs.gnu.org
Subject: bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot)
Date: Tue, 02 Feb 2016 03:17:09 -0500 [thread overview]
Message-ID: <87io2734sa.fsf@netris.org> (raw)
In-Reply-To: <87bn8hi6d2.fsf@dustycloud.org> (Christopher Allan Webber's message of "Tue, 19 Jan 2016 13:50:58 -0800")
Hi,
Christopher Allan Webber <cwebber@dustycloud.org> writes:
> Ludovic Courtès writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> Christopher Allan Webber <cwebber@dustycloud.org> writes:
>>>
>>>> From e60db83ffff23c57ec5c44de7c99cee8e4e353ff Mon Sep 17 00:00:00 2001
>>>> From: Christopher Allan Webber <cwebber@dustycloud.org>
>>>> Date: Sun, 17 Jan 2016 20:34:25 -0800
>>>> Subject: [PATCH] gnu: Add linux-libre-4.2.5
>>>>
>>>> This older version of linux-libre is being added because it was found
>>>> that newer versions (or at least 4.3.3) of linux-libre were not reading
>>>> the hardware clock on (at least Libreboot-enabled) Thinkpad x200
>>>> machines.
>>>>
>>>> * gnu/linux.scm (linux-libre-4.2.5): New variable.
>>>
>>> I would say that the variable should be named 'linux-libre-4.2', which
>>> would always be bound to the latest 4.2.x. However, there's another
>>> problem: the 4.2 branch is no longer supported upstream, so it will no
>>> longer receive security updates and other important fixes.
>>>
>>> I suggest that we instead add linux-libre-4.1, which is still supported
>>> upstream and is designated as an LTS branch. Would that be okay?
>>
>> If it works for Christopher, that’s a good idea.
>
> Fine by me, assuming it works. I can test it works fine probably tomorrow.
I just added a 'linux-libre-4.1' variable. Can you test to make sure it
works for you? I'd like to remove linux-libre-4.2.5 ASAP because 4.2.x
is no longer supported upstream and contains security flaws.
Thanks!
Mark
next prev parent reply other threads:[~2016-02-02 8:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 15:24 bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot) Christopher Allan Webber
2015-12-31 20:27 ` Mark H Weaver
2016-01-04 3:37 ` Christopher Allan Webber
2016-01-01 15:28 ` Ludovic Courtès
2016-01-04 3:39 ` Christopher Allan Webber
2016-01-04 15:02 ` Ludovic Courtès
2016-01-05 15:40 ` Christopher Allan Webber
2016-01-14 18:55 ` Christopher Allan Webber
2016-01-15 9:35 ` Ludovic Courtès
2016-01-17 16:51 ` Christopher Allan Webber
2016-01-18 16:58 ` Christopher Allan Webber
2016-01-18 19:42 ` Christopher Allan Webber
2016-01-18 22:42 ` Ludovic Courtès
2016-01-18 23:11 ` Christopher Allan Webber
2016-01-19 16:33 ` Mark H Weaver
2016-01-19 17:07 ` Ludovic Courtès
2016-01-19 17:11 ` Mark H Weaver
2016-01-19 21:50 ` Christopher Allan Webber
2016-02-02 8:17 ` Mark H Weaver [this message]
2016-02-05 13:08 ` Ludovic Courtès
2016-02-05 15:23 ` Mark H Weaver
2016-01-12 7:19 ` bug#22274: epochfail Francis Rowe
2016-01-12 19:03 ` Leo Famulari
2016-01-18 17:02 ` Christopher Allan Webber
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=87io2734sa.fsf@netris.org \
--to=mhw@netris.org \
--cc=22274@debbugs.gnu.org \
--cc=cwebber@dustycloud.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).