From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] tools/env: add posibility to inject configuration
Date: Mon, 17 Oct 2011 22:14:55 +0200 [thread overview]
Message-ID: <20111017201455.166FE140797D@gemini.denx.de> (raw)
In-Reply-To: <1314804368-25687-1-git-send-email-biessmann@corscience.de>
Dear =?UTF-8?q?Andreas=20Bie=C3=9Fmann?=,
In message <1314804368-25687-1-git-send-email-biessmann@corscience.de> you wrote:
> If one wants to use fw_printenv/fw_setenv in special variants (eg compiled in
> MTD parameters without configuration file) he needs to change the sources.
> This patch add the posibillity to change the behaviour of fw_printenv by
> defining a specific configuration header at compile time.
...
> +/tools/env/fw_env_config.h
Instead of putting this (generated) file into tools/env/, we better
put it into include/generated/
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
In a survey taken several years ago, all incoming freshmen at MIT
were asked if they expected to graduate in the top half of their
class. Ninety-seven percent responded that they did.
next prev parent reply other threads:[~2011-10-17 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 10:06 [U-Boot] [PATCH] tools/env: add posibility to inject configuration Andreas Bießmann
2011-08-31 14:39 ` Mike Frysinger
2011-08-31 15:26 ` [U-Boot] [PATCH v2] " Andreas Bießmann
2011-10-17 9:10 ` Andreas Bießmann
2011-10-17 20:14 ` Wolfgang Denk [this message]
2011-10-18 8:03 ` [U-Boot] [PATCH v3] " Andreas Bießmann
2011-11-29 9:08 ` Andreas Bießmann
2012-01-24 9:10 ` [U-Boot] [PATCH v4] " Andreas Bießmann
2012-02-20 16:37 ` Andreas Bießmann
2012-10-16 0:40 ` Joe Hershberger
2012-10-16 9:43 ` Andreas Bießmann
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=20111017201455.166FE140797D@gemini.denx.de \
--to=wd@denx.de \
--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