From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] board/pc: ensure grub.cfg is copied to target filesystem
Date: Mon, 31 Dec 2018 18:48:23 +0100 [thread overview]
Message-ID: <20181231184823.62631e32@windsurf> (raw)
In-Reply-To: <20181011222445.21185-1-greg@quimbo.fr>
Hello,
On Fri, 12 Oct 2018 00:24:45 +0200, Gr?goire Delattre wrote:
> From: Gr?goire Delattre <gregoire.delattre@gmail.com>
>
> Before this commit, the grub configuration file was copied to the
> TARGET_DIR in a post-image hook, after the filesystem has been
> generated. It was kinda working because the board/pc's grub
> configuration and the default one are the same and the later was
> copied during the build process of the grub2 package.
>
> This commit ensures the custom board/pc grub configuration is copied at
> the right time.
>
> Signed-off-by: Gr?goire Delattre <gregoire.delattre@gmail.com>
> ---
> board/pc/post-build.sh | 15 +++++++++++++++
> board/pc/post-image.sh | 14 --------------
> configs/pc_x86_64_bios_defconfig | 3 ++-
> configs/pc_x86_64_efi_defconfig | 3 ++-
> 4 files changed, 19 insertions(+), 16 deletions(-)
> create mode 100755 board/pc/post-build.sh
> delete mode 100755 board/pc/post-image.sh
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-31 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 14:33 [Buildroot] [PATCH 1/1] board/pc: improve image generation Grégoire Delattre
2018-10-11 19:49 ` Thomas Petazzoni
2018-10-11 22:24 ` [Buildroot] [PATCH v2 1/1] board/pc: ensure grub.cfg is copied to target filesystem Grégoire Delattre
2018-10-21 23:58 ` Matthew Weber
2018-12-31 17:48 ` Thomas Petazzoni [this message]
2019-01-23 15:19 ` Peter Korsgaard
[not found] ` <20181011223946.cqtbipkwm2gyviiu@lois>
2018-10-12 11:04 ` [Buildroot] [PATCH 1/1] board/pc: improve image generation Thomas Petazzoni
2018-10-12 11:21 ` Grégoire Delattre
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=20181231184823.62631e32@windsurf \
--to=thomas.petazzoni@bootlin.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