From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: Sughosh Ganu <sughosh.ganu@linaro.org>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
Malte Schmidt <malte.schmidt-oss@weidmueller.com>,
Michal Simek <michal.simek@amd.com>
Subject: Re: [PATCH v8 4/9] sandbox: Build the mkeficapsule tool for the sandbox variants
Date: Tue, 15 Aug 2023 10:46:45 -0400 [thread overview]
Message-ID: <20230815144645.GX3630934@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0DpYY3X9w66N6G0tgAwoN_3-SToTT+2yMmk0Gibse8fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Tue, Aug 15, 2023 at 08:44:18AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Sun, 13 Aug 2023 at 08:43, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Sun, Aug 13, 2023 at 07:36:45AM -0600, Simon Glass wrote:
[snip]
> > > I see what you are saying, but from my side I am trying to enumerate
> > > the boards, since generally I (like) build things without explicitly
> > > specifying each board defconfig.
> >
> > Yes, but that's not possible in this case I think. And I'm really just
> > trying to figure out how we can make CI a little easier. But maybe we
> > can't / don't bother in this case and keep fixing up the sandbox
> > defconfig files as needed.
>
> Maybe...it sounds like you are really just wanting a way for buildman
> to manually build a single board with some config added, rather than
> having it detect and build everything that is in-tree?
What I'm trying to do really, is since you didn't seem to see the value
in config fragments before, showcase how it would be beneficial to
sandbox (and CI) if we used them there.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-08-15 14:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 14:23 [PATCH v8 0/9] Enable EFI capsule generation through binman Sughosh Ganu
2023-08-10 14:23 ` [PATCH v8 1/9] binman: bintool: Build a tool from a list of commands Sughosh Ganu
2023-08-10 14:23 ` [PATCH v8 2/9] nuvoton: npcm845-evb: Add a newline at the end of file Sughosh Ganu
2023-08-10 14:23 ` [PATCH v8 3/9] sandbox: capsule: Add keys and certificates needed for capsule update testing Sughosh Ganu
2023-08-10 14:23 ` [PATCH v8 4/9] sandbox: Build the mkeficapsule tool for the sandbox variants Sughosh Ganu
2023-08-10 15:52 ` Tom Rini
2023-08-10 17:09 ` Sughosh Ganu
2023-08-10 17:17 ` Tom Rini
2023-08-11 10:59 ` Sughosh Ganu
2023-08-11 13:58 ` Tom Rini
2023-08-11 14:23 ` Sughosh Ganu
2023-08-11 14:26 ` Simon Glass
2023-08-11 14:31 ` Sughosh Ganu
2023-08-11 15:56 ` Tom Rini
2023-08-12 13:08 ` Simon Glass
2023-08-12 14:22 ` Tom Rini
2023-08-12 14:24 ` Simon Glass
2023-08-12 14:28 ` Tom Rini
2023-08-12 17:03 ` Simon Glass
2023-08-12 22:37 ` Tom Rini
2023-08-13 0:14 ` Simon Glass
2023-08-13 12:40 ` Tom Rini
2023-08-13 13:36 ` Simon Glass
2023-08-13 14:43 ` Tom Rini
2023-08-15 14:44 ` Simon Glass
2023-08-15 14:46 ` Tom Rini [this message]
2023-08-15 14:50 ` Simon Glass
2023-08-10 17:27 ` Simon Glass
2023-08-11 11:23 ` Sughosh Ganu
2023-08-11 13:36 ` Simon Glass
2023-08-11 14:24 ` Sughosh Ganu
2023-08-11 23:43 ` Takahiro Akashi
2023-08-10 14:23 ` [PATCH v8 5/9] btool: mkeficapsule: Add a bintool for EFI capsule generation Sughosh Ganu
2023-08-10 17:27 ` Simon Glass
2023-08-10 14:23 ` [PATCH v8 6/9] binman: capsule: Add support for generating EFI capsules Sughosh Ganu
2023-08-10 17:27 ` Simon Glass
2023-08-10 14:23 ` [PATCH v8 7/9] sandbox: capsule: Generate capsule related files through binman Sughosh Ganu
2023-08-10 17:27 ` Simon Glass
2023-08-10 18:41 ` Sughosh Ganu
2023-08-10 21:35 ` Simon Glass
2023-08-10 14:23 ` [PATCH v8 8/9] doc: Add documentation to highlight capsule generation related updates Sughosh Ganu
2023-08-10 15:28 ` Heinrich Schuchardt
2023-08-10 14:23 ` [PATCH v8 9/9] sandbox: trace: Increase trace buffer size Sughosh Ganu
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=20230815144645.GX3630934@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--cc=malte.schmidt-oss@weidmueller.com \
--cc=michal.simek@amd.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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