From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH ATMEL REWORK][V2] update arm/at91rm9200 work with rework rework110202
Date: Sat, 19 Feb 2011 17:22:21 +0100 [thread overview]
Message-ID: <4D5FEE3D.2000500@scharsoft.de> (raw)
In-Reply-To: <20110211201307.E4E341519FD@gemini.denx.de>
Am 11.02.2011 21:13, schrieb Wolfgang Denk:
> Dear Reinhard Meyer,
>
> In message <4D5597A8.9050605@emk-elektronik.de> you wrote:
>> Dear Wolfgang Denk,
>>> Dear Jens Scharsig,
>>>
>>> In message<4D5573CA.9000501@scharsoft.de> you wrote:
>>>> * convert at91rm9200ek and eb_cpux9k2 board to ATMEL_xxx name scheme
>>>> * Fix: timer.c compile error io.h not found with arm/at91rm9200
>>>> * update arm920t/at91 to ATMEL_xxx name scheme
>>>> * update arm920t/at91 soc lib
>>>> * update at91_emac driver
>>> ...
>>>> /* Port B */
>>>> -#define AT91_PMX_BA_ERXCK 0x00080000
>>>> -#define AT91_PMX_BA_ECOL 0x00040000
>>>> -#define AT91_PMX_BA_ERXDV 0x00020000
>>>> -#define AT91_PMX_BA_ERX3 0x00010000
>>>> -#define AT91_PMX_BA_ERX2 0x00008000
>>> ----------------------------^^^
>>>
>>> Please, no space before tabs
>> Those lines that are being removed by the patch.
>
> Oops. I marked the wrong line.
>
> I meant this one:
>
> -> checkpatch ~/Mail/U-Boot/3377
> WARNING: please, no space before tabs
> #379: FILE: arch/arm/include/asm/arch-at91/at91rm9200.h:112:
> +#define ATMEL_PMX_BA_ERX2 ^I0x00008000$
>
>
>
> Best regards,
>
> Wolfgang Denk
>
I don't know, why my checkpatch version does not report this.
But I have fix this in V3 of the Patch.
Best regards,
Jens Scharsig
next prev parent reply other threads:[~2011-02-19 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 17:37 [U-Boot] [PATCH ATMEL REWORK][V2] update arm/at91rm9200 work with rework rework110202 Jens Scharsig
2011-02-11 19:24 ` Wolfgang Denk
2011-02-11 20:10 ` Reinhard Meyer
2011-02-11 20:13 ` Wolfgang Denk
2011-02-19 16:22 ` Jens Scharsig [this message]
2011-02-19 19:47 ` 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=4D5FEE3D.2000500@scharsoft.de \
--to=js_at_ng@scharsoft.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