From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nils Gillmann Subject: bug#32840: linux-libre 4.18.9: shpchp is no longer a module (now: built-in) Date: Wed, 26 Sep 2018 16:27:19 +0000 Message-ID: <20180926162719.ab6vx3divs4upheu@abyayala> References: <20180925195720.nelxr55dy7ntupma@abyayala> <87lg7pgcva.fsf@netris.org> <87tvmc6ap2.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g5CeZ-0008Ce-5s for bug-guix@gnu.org; Wed, 26 Sep 2018 12:27:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g5CeU-0001K1-O7 for bug-guix@gnu.org; Wed, 26 Sep 2018 12:27:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:51344) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g5CeU-0001Js-Jc for bug-guix@gnu.org; Wed, 26 Sep 2018 12:27:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g5CeU-0007JU-Cb for bug-guix@gnu.org; Wed, 26 Sep 2018 12:27:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87tvmc6ap2.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: 32840@debbugs.gnu.org, Nils Gillmann Ricardo Wurmus transcribed 808 bytes: > > Mark H Weaver writes: > > > Nils Gillmann 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. Thanks! I'll get back if this didn't fix upgrading the server. > 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? There are modules [M] and boolean y/n "builtins" in Linux. We don't need to build it as a module now, since upstream changed it to be a builtin. It is not covered by whatever selection we have in the kernel config as builtins. Since the module disappeared, users of the module were left with the choice to remove it and either build their own kernel variation or ask for it as a feature. I asked for it, since Taler wanted as little reliance on third-party repositories as possible, no matter how reliable the repositories are. > -- > Ricardo > > > >