Date: Sun, 22 Jun 2014 11:53:29 -0300
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: linux-kernel@vger.kernel.org,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Guido =?iso-8859-1?Q?Mart=EDnez?= <guido@vanguardiasur.com.ar>
Subject: Re: [PATCH] init: Introduce 'noinitramfs' kernel parameter
Message-ID: <20140622145329.GA19936@khazad-dum.debian.net>
References: <1403415685-21455-1-git-send-email-ezequiel@vanguardiasur.com.ar>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1403415685-21455-1-git-send-email-ezequiel@vanguardiasur.com.ar>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org

On Sun, 22 Jun 2014, Ezequiel Garcia wrote:
> This commit adds a new kernel parameter to provide such option, following the
> naming of the current 'initrd' which serves a similar purpose, for an initial
> RAM disk.

How does it interact with the early initramfs?

Maybe we should have the options to ignore both, ignore just the early
initramfs (to skip microcode updates and ACPI table updates), and ignore
just the main initramfs?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/