From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] board/qemu/ppc64le-powernv8: fixup example
Date: Sat, 12 Aug 2023 21:54:44 +0200 [thread overview]
Message-ID: <20230812215444.0af6eb62@windsurf> (raw)
In-Reply-To: <ZNew/asuEOItVTZZ@waldemar-brodkorb.de>
On Sat, 12 Aug 2023 18:19:09 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> Use full relative pathes for rootfs and kernel, like in other
> readme's.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> board/qemu/ppc64le-powernv8/readme.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks. I was initially a bit confused because all
those readme.txt files for Qemu configurations are used in our Gitlab
CI infra to automatically boot the resulting kernel/rootfs images in
Qemu, and the build/test was working fine in our CI.
Turns out that board/qemu/post-image.sh strips output/images/, and then
board/qemu/start-qemu.sh.in chdir into ${BINARIES_DIR}. So indeed, it
makes sense that both this incorrect readme.txt, and all the other ones
for Qemu defconfigs, that had output/images, worked.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-12 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 16:19 [Buildroot] [PATCH] board/qemu/ppc64le-powernv8: fixup example Waldemar Brodkorb
2023-08-12 19:54 ` Thomas Petazzoni via buildroot [this message]
2023-09-12 18:04 ` Peter Korsgaard
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=20230812215444.0af6eb62@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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