All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@moreton.com.au>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 1/2] add Kendein/Micrel KS8695P CPU support
Date: Fri, 20 May 2005 23:52:16 +1000	[thread overview]
Message-ID: <428DEB90.1010905@moreton.com.au> (raw)
In-Reply-To: <20050519224735.64CE4C1512@atlas.denx.de>

Hi Wolfgang,

Wolfgang Denk wrote:
> The subject ("[PATCH 1/2]") indicates that there is a second part  to
> follow - is there? I don't see any obvious stuff missing?

No, that was all the CPU support. I just reply'ed to the
first email. The new patch was a bit smaller, and fitted all
in that one email.

> But please stick to the Coding Style:
> don't add trailing white space to files
> (cpu/arm920t/ks8695/lowlevel_init.S,
> include/asm-arm/arch-ks8695/platform.h),
> don't add trailing empty lines
> (cpu/arm920t/ks8695/interrupts.c),
> and don't use C++ comments
> (drivers/ks8695eth.c).

Sure thing. Old habits :-)

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg at snapgear.com
SnapGear -- a CyberGuard Company            PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

      parent reply	other threads:[~2005-05-20 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 14:22 [U-Boot-Users] [PATCH 1/2] add Kendein/Micrel KS8695P CPU support Greg Ungerer
2005-05-17 14:53 ` Wolfgang Denk
2005-05-19 14:26   ` Greg Ungerer
2005-05-19 22:47     ` Wolfgang Denk
2005-05-20  9:20       ` richard at uclinux.net
2005-05-20 15:44         ` Wolfgang Denk
2005-05-23  1:22           ` Greg Ungerer
2005-05-23 11:08             ` Wolfgang Denk
2005-05-24  6:45               ` Greg Ungerer
2005-05-20 13:52       ` Greg Ungerer [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=428DEB90.1010905@moreton.com.au \
    --to=gerg@moreton.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.