Re: [PATCH 0/6] Attempt to enforce standard extensions for build output

public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed

From: Michael Walle <michael@walle.cc>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Tom Rini <trini@konsulko.com>,
	Alper Nebi Yasak <alpernebiyasak@gmail.com>,
	Dillon Min <dillon.minfei@gmail.com>,
	Ivan Mikhaylov <fr0st61te@gmail.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Kamil Lulko <kamil.lulko@gmail.com>, Marek Vasut <marex@denx.de>,
	Neha Malcom Francis <n-francis@ti.com>,
	Patrice Chotard <patrice.chotard@foss.st.com>,
	Patrick Delaunay <patrick.delaunay@foss.st.com>,
	Peng Fan <peng.fan@nxp.com>,
	Philippe Reynes <philippe.reynes@softathome.com>,
	Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>,
	Vikas Manocha <vikas.manocha@st.com>,
	u-boot@dh-electronics.com,
	uboot-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 0/6] Attempt to enforce standard extensions for build output
Date: Thu, 24 Aug 2023 16:55:52 +0200	[thread overview]
Message-ID: <6cb6ee52ccd550d3c8fddd76bc84a282@walle.cc> (raw)
In-Reply-To: <CAPnjgZ0MNb5aAtmz9Yk+JiHxQt+qwhQW=WccgiiRRqfQ-a1OBQ@mail.gmail.com>

Hi,

>> > This series adjusts binman to enforce just 4 extensions for output
>> > images:
>> >
>> >    .bin
>> >    .rom
>> >    .itb
>> >    .img
>> >
>> > Other extensions will produce an error. With this rule observed,
>> > buildman
>> > can keep the required files.
>> 
>> How does this work? I didn't get all the patches from this series, 
>> which
>> makes
>> it really hard to review or ack the individual patches.
>> 
>> Are we just whitelisting any files with these extension? Honestly, 
>> this
>> sounds like an arbitrary restriction to me. But maybe I'm missing some
>> context.
> 
> You can see the full series here:
> 
> https://patchwork.ozlabs.org/project/uboot/list/?series=370121

I know the archives/patchwork. All I was saying is that sending just 
parts
of a patch series to specific ppl doesn't make any sense, because you 
always
miss the context and for that you have to look at the archives.

-michael

next prev parent reply	other threads:[~2023-08-24 14:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  3:02 [PATCH 0/6] Attempt to enforce standard extensions for build output Simon Glass
2023-08-24  3:02 ` [PATCH 1/6] binman: Require image filenames to have certain extensions Simon Glass
2023-08-24  3:02 ` [PATCH 2/6] buildman: Keep all permitted output files Simon Glass
2023-08-24 14:26   ` Tom Rini
2023-08-24  3:02 ` [PATCH 3/6] buildman: Show progress when regenerating the board.cfg file Simon Glass
2023-08-24  3:02 ` [PATCH 4/6] buildman: Start the clock when the build starts Simon Glass
2023-08-24  3:02 ` [PATCH 5/6] kontron_sl28: Use u-boot-update.bin instead of u-boot.update Simon Glass
2023-08-24  7:35   ` Michael Walle
2023-08-24  3:02 ` [PATCH 6/6] stm32mp15: Use u-boot-spl-stm32.bin instead of u-boot-spl.stm32 Simon Glass
2023-08-24  3:12   ` Marek Vasut
2023-08-24 14:25     ` Tom Rini
2023-08-24 15:09       ` Marek Vasut
2023-08-24 15:14         ` Tom Rini
2023-08-24 15:26           ` Marek Vasut
2023-08-29 16:28           ` Patrick DELAUNAY
2023-09-02  0:09             ` Simon Glass
2023-08-24  7:32 ` [PATCH 0/6] Attempt to enforce standard extensions for build output Michael Walle
2023-08-24 14:43   ` Simon Glass
2023-08-24 14:55     ` Michael Walle [this message]
2023-08-24 12:26 ` Neha Malcom Francis
2023-08-24 14:41   ` Simon Glass
2023-08-24 13:38 ` Tom Rini
2023-08-24 14:41   ` Simon Glass
2023-08-24 14:45     ` Tom Rini
2023-08-24 14:49       ` Simon Glass
2023-08-24 15:16         ` Tom Rini
2023-08-27 19:17 ` Alper Nebi Yasak
2023-08-28 17:54   ` Simon Glass
2023-08-28 18:53     ` Tom Rini
2023-08-31 10:20     ` Alper Nebi Yasak
2023-08-31 19:01       ` Simon Glass
2023-08-31 19:07         ` Tom Rini
2023-08-31 19:22           ` Simon Glass
2023-08-31 19:24             ` Tom Rini
2023-09-01  1:10               ` Simon Glass

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=6cb6ee52ccd550d3c8fddd76bc84a282@walle.cc \
    --to=michael@walle.cc \
    --cc=alpernebiyasak@gmail.com \
    --cc=dillon.minfei@gmail.com \
    --cc=fr0st61te@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kamil.lulko@gmail.com \
    --cc=marex@denx.de \
    --cc=n-francis@ti.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=peng.fan@nxp.com \
    --cc=philippe.reynes@softathome.com \
    --cc=sjg@chromium.org \
    --cc=stefan.herbrechtsmeier@weidmueller.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@dh-electronics.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-stm32@st-md-mailman.stormreply.com \
    --cc=vikas.manocha@st.com \
    /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