All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] initramfs: drop comment against multiple formats
Date: Fri, 25 Jan 2019 19:19:01 -0500	[thread overview]
Message-ID: <20190126001901.3090-1-vivien.didelot@gmail.com> (raw)

This patch removes an old comment against having multiple filesystem
formats which doesn't bring any value.

It is also wrong per-se: one may want to use Buildroot to prepare a
custom distribution containing a kernel+initramfs and a persistent
default rootfs to pivot to.

Signed-off-by: Vivien Didelot <vivien.didelot@gmail.com>
---
 fs/initramfs/Config.in | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/fs/initramfs/Config.in b/fs/initramfs/Config.in
index 9d5a3f92e6..42a9d60524 100644
--- a/fs/initramfs/Config.in
+++ b/fs/initramfs/Config.in
@@ -13,10 +13,5 @@ config BR2_TARGET_ROOTFS_INITRAMFS
 	  is used, regardless of how buildroot's cpio archive is
 	  configured.
 
-	  Note that enabling initramfs together with another filesystem
-	  formats doesn't make sense: you would end up having two
-	  identical root filesystems, one embedded inside the kernel
-	  image, and one separately.
-
 comment "initramfs needs a Linux kernel to be built"
 	depends on !BR2_LINUX_KERNEL
-- 
2.20.1

             reply	other threads:[~2019-01-26  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26  0:19 Vivien Didelot [this message]
2019-01-26  9:56 ` [Buildroot] [PATCH] initramfs: drop comment against multiple formats Peter Korsgaard
2019-01-26 16:59   ` Vivien Didelot
2019-06-23 16:09 ` Thomas Petazzoni
2019-06-25 15:14   ` Vivien Didelot

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=20190126001901.3090-1-vivien.didelot@gmail.com \
    --to=vivien.didelot@gmail.com \
    --cc=buildroot@busybox.net \
    /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. 
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.