From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH v2 2/2] binman: Write fake blobs to the output directory
Date: Thu, 13 Jan 2022 07:53:42 -0500 [thread overview]
Message-ID: <20220113125342.GI9207@bill-the-cat> (raw)
In-Reply-To: <20220112201036.300649-2-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On Wed, Jan 12, 2022 at 01:10:36PM -0700, Simon Glass wrote:
> At present binman writes fake blobs to the current directory. This is not
> very helpful, since the files serve no useful purpose once binman has
> finished. They clutter up the source directory and affect future runs,
> since the files in the current directory are often used in preference to
> those in the board directory.
>
> To avoid these problems, write them to the output directory instead.
>
> Move the file-creation code to the Entry base class, so it can be used by
> any entry type that needs it. This is required since some entry types,
> such as Entry_blob_ext_list, are not subclasses of Entry_blob.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-13 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 20:10 [PATCH v2 1/2] binman: Renumber the fake blob dts Simon Glass
2022-01-12 20:10 ` [PATCH v2 2/2] binman: Write fake blobs to the output directory Simon Glass
2022-01-13 12:53 ` Tom Rini [this message]
2022-01-13 12:53 ` [PATCH v2 1/2] binman: Renumber the fake blob dts Tom Rini
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=20220113125342.GI9207@bill-the-cat \
--to=trini@konsulko.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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