From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pxa: Fix typo in GCDR(x)
Date: Sat, 01 Aug 2009 22:09:03 +0200 [thread overview]
Message-ID: <20090801200903.3CDCA832E416@gemini.denx.de> (raw)
In-Reply-To: <d47469d30908011215k51f1ff58j47892a3e86c40a17@mail.gmail.com>
Dear David Hunter,
In message <d47469d30908011215k51f1ff58j47892a3e86c40a17@mail.gmail.com> you wrote:
>
> That raises a question. I'm porting U-Boot to our Marvell PXA310-based
> hardware. (I'm very new to contributing to an open source project
> using git, so I apologize in advance for the mistakes I'll make out of
> ignorance.) I have a few patches queued which will attempt to clean up
Please see http://www.denx.de/wiki/U-Boot/Patches for details.
> and improve PXA300/310/320 support -- register definitions for now,
> but later driver stuff as I dive into Ethernet, etc.. Which branch
> should I be basing my work on: u-boot, -arm, or -pxa?
Normally please use the "master" branch of the mainline U-Boot git
repository (git://git.denx.de/u-boot.git) as reference, unless
(usually late in a release cycle) there has been an announcement to
use the "next" branch of this repository instead.
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 English, every word can be verbed. Would that it were so in our
programming languages.
prev parent reply other threads:[~2009-08-01 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 21:32 [U-Boot] [PATCH] pxa: Fix typo in GCDR(x) David Hunter
2009-08-01 13:28 ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-01 19:15 ` David Hunter
2009-08-01 19:36 ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-01 20:09 ` 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=20090801200903.3CDCA832E416@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