From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH] linux: add external initramfs options
Date: Mon, 9 Jun 2014 15:34:38 +0200 [thread overview]
Message-ID: <20140609153438.0de69bcb@free-electrons.com> (raw)
In-Reply-To: <1401138097-11024-1-git-send-email-guido@vanguardiasur.com.ar>
Dear Guido Mart?nez,
On Mon, 26 May 2014 18:01:37 -0300, Guido Mart?nez wrote:
> This patch allows building the kernel with an external initramfs. This
> is useful in cases where one wants to generate the kernel and rootfs
> with BR, and the kernel needs to contain an initramfs different to the
> rootfs.
>
> The path specified can be a cpio archive or a directory, just like
> the kernel config. The path is specified w.r.t. BRs topdir, and made
> absolute since the kernel builds in another directory.
>
> Signed-off-by: Guido Mart?nez <guido@vanguardiasur.com.ar>
Since I agree with the feedback from Arnout, I'll mark this as Rejected
in patchwork. There's no point in duplicating each and every kernel
configuration option at the Buildroot level. Just make sure to tune
your kernel configuration properly, and pass it to Buildroot as the
kernel configuration file.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-06-09 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 21:01 [Buildroot] [RFC/PATCH] linux: add external initramfs options Guido Martínez
2014-05-28 16:47 ` Arnout Vandecappelle
2014-06-04 20:45 ` Ezequiel Garcia
2014-06-04 22:29 ` Arnout Vandecappelle
2014-06-09 14:09 ` Ezequiel Garcia
2014-06-09 13:34 ` Thomas Petazzoni [this message]
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=20140609153438.0de69bcb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox