From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fw_env.h: added a few missing defines
Date: Thu, 05 Jan 2012 16:07:52 +0100 [thread overview]
Message-ID: <20120105150752.C843C82518@gemini.denx.de> (raw)
In-Reply-To: <1325512063-15583-1-git-send-email-fransmeulenbroeks@gmail.com>
Dear Frans Meulenbroeks,
In message <1325512063-15583-1-git-send-email-fransmeulenbroeks@gmail.com> you wrote:
> The README file lists 4 defined that were not actually present in the .h
> file but that were needed to get things working with settings compiled in.
> They are
> Added these to the .h file
> (the values above are the ones from the README file)
>
> Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
> ---
> Noticed this was not applied and still pending in my git tree
> Couldn't find a trace that I actually posted it so here it is (possibly again)
>
> tools/env/fw_env.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
Applied, thanks.
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
I've been programming for (35-9=) 24 years myself, and I find the
best way to learn a new language is to *read* every example snippet I
can find, with a reference book close by. Eventually, the *rhythm* of
the language starts pounding in my head... and my fluency is close at
hand. That's how I learned Perl, and now I'm one of the drummers. :-)
-- Randal L. Schwartz in <8cvi6p2tir.fsf@gadget.cscaper.com>
next prev parent reply other threads:[~2012-01-05 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 13:47 [U-Boot] [PATCH] fw_env.h: added a few missing defines Frans Meulenbroeks
2012-01-05 15:07 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-01 13:30 Frans Meulenbroeks
2011-12-01 15:21 ` Andreas Bießmann
2011-12-02 8:24 ` Frans Meulenbroeks
2011-12-02 10:13 ` 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=20120105150752.C843C82518@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