all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: David Craven <david@craven.ch>
Cc: help-guix@gnu.org, Dmitri Anikin <anarki@teknik.io>
Subject: Re: Custom kernel
Date: Sun, 11 Dec 2016 14:58:31 -0500	[thread overview]
Message-ID: <877f769r14.fsf@netris.org> (raw)
In-Reply-To: <CAL1_imkTp8PVbQCS4rV=8APXkCDD-PgOAhQuGVKro0HoCv8kdQ@mail.gmail.com> (David Craven's message of "Sun, 11 Dec 2016 15:59:52 +0100")

I wrote:
>> For example, when I recently added security fixes to linux-libre, I needed
>> to add the patches in two separate places, and every time I update the
>> version, I need to update two places as well.

David Craven <david@craven.ch> responded:
> I believe this was on purpose to avoid having to rebuild two kernels
> every time.

My understanding is that most stable kernel updates contain security
fixes.  In any case, upstream has a deliberate policy of refusing to
specify which updates are security-critical, so we must assume that they
all are.  I'm not comfortable leaving non-Intel kernels with unpatched
security flaws.

> I was impatient to get this stuff into master because my linux libre
> arm kernel wasn't building on the beagle bone black (not enough RAM).
> I think some more patience could have made things better =P

Yes, of course, that makes sense.  I very much appreciate your work on
this.

     Thanks,
       Mark

  reply	other threads:[~2016-12-11 19:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01 12:34 Custom kernel Dmitri Anikin
2016-12-02 14:50 ` Ludovic Courtès
2016-12-11 14:11   ` Mark H Weaver
2016-12-11 14:59     ` David Craven
2016-12-11 19:58       ` Mark H Weaver [this message]
2016-12-11 22:10     ` Ludovic Courtès
2016-12-12 20:13       ` Mark H Weaver
2016-12-12 22:44         ` Ludovic Courtès
2016-12-05  8:58 ` Dmitri Anikin
2016-12-05  9:33   ` Ludovic Courtès

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=877f769r14.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=anarki@teknik.io \
    --cc=david@craven.ch \
    --cc=help-guix@gnu.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.