From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: "U-Boot Mailing List" <u-boot@lists.denx.de>,
"Michal Simek" <monstr@monstr.eu>,
"huang lin" <hl@rock-chips.com>,
"Jeffy Chen" <jeffy.chen@rock-chips.com>,
"Kever Yang" <kever.yang@rock-chips.com>,
"Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>,
"NXP i . MX U-Boot Team" <uboot-imx@nxp.com>,
"Marek Behún" <marek.behun@nic.cz>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>
Subject: Re: [PATCH v2 2/2] Makefile: Don't allow new boards with SPL_FIT_GENERATOR
Date: Mon, 31 Jan 2022 09:24:12 -0500 [thread overview]
Message-ID: <20220131142412.GH7515@bill-the-cat> (raw)
In-Reply-To: <20220130155225.726890-2-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
On Sun, Jan 30, 2022 at 08:52:25AM -0700, Simon Glass wrote:
> More than a year after this migration message appeared, we still have new
> boards being added with this option. Add a check against this.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Please just make this an error in checkpatch.pl instead.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-31 14:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 15:52 [PATCH v2 1/2] Makefile: Create a file to indicate the config Simon Glass
2022-01-30 15:52 ` [PATCH v2 2/2] Makefile: Don't allow new boards with SPL_FIT_GENERATOR Simon Glass
2022-01-30 19:40 ` Michal Simek
2022-01-30 23:14 ` Simon Glass
2022-01-31 14:24 ` Tom Rini [this message]
2022-01-31 16:13 ` Simon Glass
2022-01-31 16:15 ` Tom Rini
2022-01-31 17:27 ` Simon Glass
2022-01-31 18:00 ` Tom Rini
2022-01-31 19:57 ` Simon Glass
2022-01-31 20:40 ` Tom Rini
2022-01-31 21:22 ` Simon Glass
2022-01-31 22:05 ` Tom Rini
2022-01-31 22:59 ` Simon Glass
2022-01-31 23:25 ` Tom Rini
2022-01-31 23:32 ` Tom Rini
2022-02-01 14:05 ` Simon Glass
2022-02-01 15:42 ` Simon Glass
2022-02-01 16:08 ` Mark Kettenis
2022-02-01 16:24 ` Simon Glass
2022-01-31 22:02 ` Mark Kettenis
2022-01-31 14:24 ` [PATCH v2 1/2] Makefile: Create a file to indicate the config Tom Rini
2022-01-31 16:13 ` Simon Glass
2022-01-31 16:21 ` Tom Rini
2022-01-31 17:27 ` 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=20220131142412.GH7515@bill-the-cat \
--to=trini@konsulko.com \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=marek.behun@nic.cz \
--cc=monstr@monstr.eu \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=yamada.masahiro@socionext.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