From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] tools/env: Fix build failure from missing header include
Date: Mon, 15 Oct 2012 16:04:53 -0700 [thread overview]
Message-ID: <20121015230453.GJ25082@bill-the-cat> (raw)
In-Reply-To: <1350073417-8866-1-git-send-email-joe.hershberger@ni.com>
On Fri, Oct 12, 2012 at 10:23:37AM -0000, Joe Hershberger wrote:
> This was introduced in:
> 8679d0ffdcc0beafea8e6942c0c67cf859afa18e -
> COMMON: Use __stringify() instead of MK_STR()
>
> The header is now needed since common.h is not included in this tool.
>
> Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121015/3aae4ae6/attachment.pgp>
prev parent reply other threads:[~2012-10-15 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 20:23 [U-Boot] [PATCH] tools/env: Fix build failure from missing header include Joe Hershberger
2012-10-12 22:20 ` Marek Vasut
2012-10-13 3:55 ` Joe Hershberger
2012-10-15 23:04 ` 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=20121015230453.GJ25082@bill-the-cat \
--to=trini@ti.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