From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 3/3] config_whitelist: remove bogus options
Date: Sat, 8 Oct 2016 13:06:57 -0400 [thread overview]
Message-ID: <20161008170657.GN4884@bill-the-cat> (raw)
In-Reply-To: <1474858350-17422-4-git-send-email-yamada.masahiro@socionext.com>
On Mon, Sep 26, 2016 at 11:52:30AM +0900, Masahiro Yamada wrote:
> These are not CONFIG options (detected by my eyes).
>
> CONFIG_SPL_BUILD and CONFIG_TPL_BUILD are build options defined only
> for building SPL and TPL, respectively.
>
> The others are just mentioned in comment blocks.
>
> Now, scripts/build-whitelist.sh never picks up new options. Once
> we kill these false ones, they will never revive.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161008/511c1711/attachment.sig>
prev parent reply other threads:[~2016-10-08 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 2:52 [U-Boot] [PATCH v3 0/3] config whitelist: tool update and sync Masahiro Yamada
2016-09-26 2:52 ` [U-Boot] [PATCH v3 1/3] build-whitelist: do not add new options to whitelist when update Masahiro Yamada
2016-10-08 17:06 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-09-26 2:52 ` [U-Boot] [PATCH v3 2/3] config_whitelist: sync by tool Masahiro Yamada
2016-10-08 17:06 ` [U-Boot] [U-Boot,v3,2/3] " Tom Rini
2016-09-26 2:52 ` [U-Boot] [PATCH v3 3/3] config_whitelist: remove bogus options Masahiro Yamada
2016-09-27 0:32 ` Simon Glass
2016-10-08 17:06 ` Tom Rini [this message]
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=20161008170657.GN4884@bill-the-cat \
--to=trini@konsulko.com \
--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