From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] configs/pc: refactor to use genimage and grub.cfg
Date: Sun, 22 Oct 2017 16:36:01 +0200 [thread overview]
Message-ID: <20171022163601.0cde6493@windsurf> (raw)
In-Reply-To: <20171022135426.28901-1-nunes.erico@gmail.com>
Hello,
On Sun, 22 Oct 2017 15:54:24 +0200, Erico Nunes wrote:
> This simplifies the pc configs and respective post image scripts to use
> the shared genimage script and separate grub config files.
> Separate grub files are cleaner to maintain and easier to copy and
> modify, for example to support booting the pc defconfigs in qemu.
>
> Signed-off-by: Erico Nunes <nunes.erico@gmail.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> Changes v1 -> v2:
> - Drop the BR2_TARGET_GRUB2_CFG proposed use since the patch was
> dropped.
> ---
> board/pc/grub-bios.cfg | 6 ++++++
> board/pc/grub-efi.cfg | 6 ++++++
> board/pc/post-image.sh | 29 ++++-------------------------
> configs/pc_x86_64_bios_defconfig | 3 ++-
> configs/pc_x86_64_efi_defconfig | 3 ++-
> 5 files changed, 20 insertions(+), 27 deletions(-)
> create mode 100644 board/pc/grub-bios.cfg
> create mode 100755 board/pc/grub-efi.cfg
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-22 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 13:54 [Buildroot] [PATCH v2 1/3] configs/pc: refactor to use genimage and grub.cfg Erico Nunes
2017-10-22 13:54 ` [Buildroot] [PATCH v2 2/3] board/pc: add documentation for testing with qemu Erico Nunes
2017-10-22 14:36 ` Thomas Petazzoni
2017-10-22 15:26 ` Peter Korsgaard
2017-10-22 13:54 ` [Buildroot] [PATCH v2 3/3] DEVELOPERS: add maintainer for pc_x86_64_* defconfigs Erico Nunes
2017-10-22 14:36 ` Thomas Petazzoni
2017-10-22 14:36 ` 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=20171022163601.0cde6493@windsurf \
--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 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.