From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] board.c config patch
Date: Fri, 27 Feb 2004 01:14:32 +0100 [thread overview]
Message-ID: <20040227001437.4EF2DC0655@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 25 Feb 2004 11:12:28 PST." <11218-23151@sneakemail.com>
In message <11218-23151@sneakemail.com> you wrote:
>
> This simple patch seems to have got lost in the frey. It is
> a simple patch that makes the use of CONFIG_SERIAL_SOFTWARE_FIFO
> consistent with other uses throughout the source.
Added, thanks - but please be more careful next time. You caught only
one of the 3 board.c files [I fixed the others, too]
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
"The majority of the stupid is invincible and guaranteed for all
time. The terror of their tyranny, however, is alleviated by their
lack of consistency." - Albert Einstein
prev parent reply other threads:[~2004-02-27 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 19:12 [U-Boot-Users] board.c config patch Stephen Williams
2004-02-27 0:14 ` Wolfgang Denk [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=20040227001437.4EF2DC0655@atlas.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