From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] README: Give an explicit example of adding a new board.
Date: Tue, 17 Nov 2009 13:01:46 +0100 [thread overview]
Message-ID: <20091117120146.9012BF51B07@gemini.denx.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0911170523040.24840@localhost>
Dear "Robert P. J. Day",
In message <alpine.LFD.2.00.0911170523040.24840@localhost> you wrote:
>
> > > + First, the new files:
> > > +
> > > + ./board/ti/beagle/
> > > + beagle.c
> > > + beagle.h
> > > + config.mk
> > > + Makefile
> > > + ./include/configs/omap3_beagle.h
> >
> > Most probably the naming convention guys here want some hints about correct
> > directory and config file names ;)
>
> just to be clear, i wasn't trying to give methodical directions for
> *how* to add a board, just a summary of what the *end result* might be
> if someone wanted to see them. so, in a sense, i'm not trying to
> duplicate the instructions for how to add a board, just let people see
> what it ultimately represents.
Then please use an example that does not lead people into doing bad
things.
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
"Though a program be but three lines long,
someday it will have to be maintained."
- The Tao of Programming
prev parent reply other threads:[~2009-11-17 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 9:22 [U-Boot] [PATCH] README: Give an explicit example of adding a new board Robert P. J. Day
2009-11-17 10:02 ` Dirk Behme
2009-11-17 10:26 ` Robert P. J. Day
2009-11-17 12:01 ` 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=20091117120146.9012BF51B07@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