From: David Craven <david@craven.ch>
To: Mark H Weaver <mhw@netris.org>
Cc: Dmitri Anikin <anarki@teknik.io>, help-guix@gnu.org
Subject: Re: Custom kernel
Date: Sun, 11 Dec 2016 15:59:52 +0100 [thread overview]
Message-ID: <CAL1_imkTp8PVbQCS4rV=8APXkCDD-PgOAhQuGVKro0HoCv8kdQ@mail.gmail.com> (raw)
In-Reply-To: <87y3zma72y.fsf@netris.org>
>> Currently ‘make-linux-libre’ is not public, but we could probably make
>> it public (David, WDYT?). In the meantime, in your own module, you can
>> do.
> I think we should avoid exporting 'make-linux-libre' in its current
> form. Although it was an improvement in some ways over what we had
> previously, I've found it to be an inadequate interface in many
> respects, and in my opinion it needs to be redesigned. I don't have
> time to make a case now, but in practice it leads to redundancy.
I agree that there is room for improvement. But I don't think it's as
easy as it may seem...
> 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.
I believe this was on purpose to avoid having to rebuild two kernels every time.
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
next prev parent reply other threads:[~2016-12-11 15:01 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 [this message]
2016-12-11 19:58 ` Mark H Weaver
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='CAL1_imkTp8PVbQCS4rV=8APXkCDD-PgOAhQuGVKro0HoCv8kdQ@mail.gmail.com' \
--to=david@craven.ch \
--cc=anarki@teknik.io \
--cc=help-guix@gnu.org \
--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.