From: Stelian Pop <stelian@popies.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 4/5] [ARM] AT91CAP9 support - board/ files
Date: Tue, 29 Jan 2008 10:03:11 +0100 [thread overview]
Message-ID: <1201597391.6265.7.camel@galileo> (raw)
In-Reply-To: <20080128212651.GB8079@game.jcrosoft.org>
Le lundi 28 janvier 2008 ? 22:26 +0100, Jean-Christophe PLAGNIOL-VILLARD
a ?crit :
> > +#define MP_BLOCK_3_BASE 0xFDF00000
[...]
> why did you defined and undefined value, specialy when you redefined the
> same value?
Copy'n'paste probably. It doesn't matter much though.
> pls remove not needed space
Sure. (btw, how do you check for such things ? kernel's checkpatch.pl
didn't see this)
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2008-01-29 9:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 10:51 [U-Boot-Users] [PATCH 0/5] [ARM] AT91CAP9 support Stelian Pop
2008-01-28 10:53 ` [U-Boot-Users] [PATCH 1/5] [ARM] AT91CAP9 support - build files Stelian Pop
2008-01-28 10:54 ` [U-Boot-Users] [PATCH 2/5] [ARM] AT91CAP9 support - cpu/ files Stelian Pop
2008-01-28 10:59 ` Stelian Pop
2008-01-28 21:15 ` Jean-Christophe PLAGNIOL-VILLARD
2008-01-29 8:55 ` Stelian Pop
2008-01-28 10:56 ` [U-Boot-Users] [PATCH 3/5] " Stelian Pop
2008-01-28 10:57 ` [U-Boot-Users] [PATCH 4/5] [ARM] AT91CAP9 support - board/ files Stelian Pop
2008-01-28 21:26 ` Jean-Christophe PLAGNIOL-VILLARD
2008-01-29 9:03 ` Stelian Pop [this message]
2008-01-28 10:58 ` [U-Boot-Users] [PATCH 5/5] [ARM] AT91CAP9 support - MACB driver changes Stelian Pop
2008-01-28 12:56 ` Haavard Skinnemoen
-- strict thread matches above, loose matches on Subject: below --
2008-01-26 23:56 [U-Boot-Users] [PATCH 0/5] [ARM] AT91CAP9 support Stelian Pop
2008-01-27 0:02 ` [U-Boot-Users] [PATCH 4/5] [ARM] AT91CAP9 support - board/ files Stelian Pop
2008-01-27 0:48 ` Wolfgang Denk
2008-01-28 10:49 ` Stelian Pop
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=1201597391.6265.7.camel@galileo \
--to=stelian@popies.net \
--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