From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fixdep: remove multiple .config support code
Date: Fri, 6 Mar 2015 10:47:40 -0500 [thread overview]
Message-ID: <20150306154740.GG25373@bill-the-cat> (raw)
In-Reply-To: <1425051477-13273-1-git-send-email-yamada.m@jp.panasonic.com>
On Sat, Feb 28, 2015 at 12:37:57AM +0900, Masahiro Yamada wrote:
> Since commit e02ee2548afe (kconfig: switch to single .config
> configuration), the ".*.cmd" files are not correctly created
> for SPL/TPL. The U-Boot extension code in fixdep, which was
> introduced to support the multiple .config, must be removed.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.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: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150306/9b99044b/attachment.sig>
prev parent reply other threads:[~2015-03-06 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 15:37 [U-Boot] [PATCH] fixdep: remove multiple .config support code Masahiro Yamada
2015-03-02 16:03 ` Simon Glass
2015-03-06 15:47 ` 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=20150306154740.GG25373@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