public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] README: Add an example of adding a new board.
Date: Wed, 18 Nov 2009 00:26:30 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911180024280.13228@localhost> (raw)
In-Reply-To: <20091117195014.7590BF51B07@gemini.denx.de>

On Tue, 17 Nov 2009, Wolfgang Denk wrote:

> Dear "Robert P. J. Day",
>
> In message <alpine.LFD.2.00.0911170707400.7159@localhost> you wrote:
> >
> > Show the simple end result of adding an example board (BeagleBoard).
> >
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> This text is still inconsistent and not good enough as an example.
>
> >   based on dirk's earlier email, i'm emphasizing that this
> > represents only the *end result* of adding BeagleBoard support to
> > U-Boot. anything more involved than that wouldn't really belong in
> > the README and would more properly be described in, say, an ARM
> > porting guide.
>
> How about adding an entry in the U-Boot wiki?

  ok, that's fair.

rday

p.s.  is there a "trivial" patch email address for simple things like
typoes, just to keep this main list for more important stuff?

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

  reply	other threads:[~2009-11-18  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 12:09 [U-Boot] [PATCH v2] README: Add an example of adding a new board Robert P. J. Day
2009-11-17 19:50 ` Wolfgang Denk
2009-11-18  5:26   ` Robert P. J. Day [this message]
2009-11-18 22:34     ` Wolfgang Denk

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=alpine.LFD.2.00.0911180024280.13228@localhost \
    --to=rpjday@crashcourse.ca \
    --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