all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: 32840-done@debbugs.gnu.org, Nils Gillmann <gillmann@n0.is>
Subject: bug#32840: linux-libre 4.18.9: shpchp is no longer a module (now: built-in)
Date: Wed, 26 Sep 2018 08:21:13 +0200	[thread overview]
Message-ID: <87tvmc6ap2.fsf@elephly.net> (raw)
In-Reply-To: <87lg7pgcva.fsf@netris.org>


Mark H Weaver <mhw@netris.org> writes:

> Nils Gillmann <gillmann@n0.is> writes:
>
>> at taler we need shpchp as a module in the initrd.
>>
>> Before version 4.18.x, shpchp was a module we've build in guix' linux-libre,
>> you were able to just specify it for the initrd.
>>
>> With 4.18.9, this module became a compile-in/built-in (see linux
>> commit log).  I want to avoid maintaining yet another kernel
>> definition for future complications if I can.  Can we get this module
>> built in by default?
>
> Done in commit fe73352e8073ea0a0e6f6b5591f24395671998ab on master.
> Closing this bug now, but please reopen if appropriate.

I don’t understand why building it as a module is needed when upstream
decided to turn it into a built-in feature.

Could you please explain?

-- 
Ricardo

  reply	other threads:[~2018-09-26  6:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 19:57 bug#32840: linux-libre 4.18.9: shpchp is no longer a module (now: built-in) Nils Gillmann
2018-09-25 23:36 ` Mark H Weaver
2018-10-17 22:59   ` Ludovic Courtès
2018-10-18  0:24     ` Mark H Weaver
2018-10-18 22:16       ` Ludovic Courtès
2018-09-26  3:24 ` Mark H Weaver
2018-09-26  6:21   ` Ricardo Wurmus [this message]
2018-09-26 16:27     ` Nils Gillmann

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=87tvmc6ap2.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=32840-done@debbugs.gnu.org \
    --cc=gillmann@n0.is \
    --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.