From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc4xx: Cleanup PMC405 board support
Date: Wed, 18 Feb 2009 14:02:17 +0100 [thread overview]
Message-ID: <200902181402.18052.sr@denx.de> (raw)
In-Reply-To: <200902180746.57288.mfuchs@ma-fu.de>
On Wednesday 18 February 2009, Matthias Fuchs wrote:
> > > I suggest to switch to using the out_be32()/in_be32() accessor
> > > functions instead. I am aware that many other 4xx boards still use the
> > > "wrong" accessor functions for initial GPIO configuration. I'll try to
> > > change this soon.
> >
> > You are right I missed these. I will update the patch and resend.
> > I will also fix the other esd boards in the next days.
>
> please take a look at my 2nd patch ("Update PMC405 ...."). It does the
> requested accessor fixes. So my first patch does nothing by style cleanup
> while the 2nd one brings some updates. I tried not to mix up
> beautyfication with functional code changes :-) So please keep these
> patches as they are :-)
OK, I'll apply your patches as they are.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-02-18 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 21:26 [U-Boot] [PATCH] ppc4xx: Cleanup PMC405 board support Matthias Fuchs
2009-02-17 14:19 ` Stefan Roese
2009-02-17 14:54 ` Matthias Fuchs
2009-02-17 15:05 ` Stefan Roese
2009-02-18 6:46 ` Matthias Fuchs
2009-02-18 13:02 ` Stefan Roese [this message]
2009-02-18 13:04 ` Stefan Roese
2009-02-18 13:11 ` Stefan Roese
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=200902181402.18052.sr@denx.de \
--to=sr@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