From: Ilya Yanok <yanok@emcraft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: make it possible to build tools unconfigured
Date: Mon, 20 Jun 2011 02:46:42 +0400 [thread overview]
Message-ID: <4DFE7C52.6030503@emcraft.com> (raw)
In-Reply-To: <201106191427.40113.vapier@gentoo.org>
Hi Mike,
On 19.06.2011 22:27, Mike Frysinger wrote:
> i might be thinking of a different env_embedded situation. a different
> problem with your patch to tools/Makefile: you copied the same logic multiple
> times which means more bitrot.
Yes, that's a good point. Your patch looks good to me. Should I write a
commit message and repost it or will you?
Regards, Ilya.
next prev parent reply other threads:[~2011-06-19 22:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 21:37 [U-Boot] [PATCH] tools: make it possible to build tools unconfigured Ilya Yanok
2011-06-18 19:03 ` Mike Frysinger
2011-06-18 20:11 ` Wolfgang Denk
2011-06-18 20:21 ` Mike Frysinger
2011-06-19 17:55 ` Ilya Yanok
2011-06-19 18:27 ` Mike Frysinger
2011-06-19 22:46 ` Ilya Yanok [this message]
2011-06-19 23:22 ` Mike Frysinger
2011-06-20 17:52 ` Scott Wood
2011-10-17 19:42 ` Wolfgang Denk
2011-10-17 20:24 ` Ilya Yanok
2011-10-17 20:35 ` Wolfgang Denk
2011-10-17 20:48 ` Ilya Yanok
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=4DFE7C52.6030503@emcraft.com \
--to=yanok@emcraft.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