From: kevin.morfitt at fearnside-systems.co.uk <kevin.morfitt@fearnside-systems.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH ARM 3/3 v3] change s3c24x0 register struct members to lower case
Date: Thu, 11 Feb 2010 20:29:14 +0000 [thread overview]
Message-ID: <4B74689A.9060008@fearnside-systems.co.uk> (raw)
In-Reply-To: <4B7454A1.70106@windriver.com>
On 11/02/2010 19:04, Tom wrote:
> Kevin Morfitt wrote:
>> Changes the names of the s3c24x0 register struct members from upper-case
>> to lower-case.
>>
>> Signed-off-by: Kevin Morfitt<kevin.morfitt@fearnside-systems.co.uk>
>> ---
>>
>> v2 changes - re-number to be 3/3
>> v3 changes - re-based to modified patch 2/3
>>
>> checkpatch.pl reports no errors. MAKEALL ARM9 reports no new warnings
>> or errors.
>>
>
> I had problem applying v2 patch 1 to u-boot-arm and u-boot-samsung
> Can you check if this patchset is correctly rebased.
It's based against Monday's u-boot-master which hasn't changed since
then. v1 was against u-boot-samsung but Wolfgang asked me to do it
against u-boot-master:
"Please adhere to posting guidelines. Patches posted ere MUST be based
either on the "master" or on the "next" trees."
http://lists.denx.de/pipermail/u-boot/2009-December/065420.html
> Please also include the whole patchset when submitting so I can test it.
> Thanks
> Tom
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature database 4859 (20100211) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
next prev parent reply other threads:[~2010-02-11 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 17:51 [U-Boot] [PATCH ARM 3/3 v3] change s3c24x0 register struct members to lower case Kevin Morfitt
2010-02-11 19:04 ` Tom
2010-02-11 20:29 ` kevin.morfitt at fearnside-systems.co.uk [this message]
2010-02-12 5:19 ` Minkyu Kang
2010-02-12 13:07 ` Tom
2010-02-13 16:06 ` Minkyu Kang
2010-02-13 17:02 ` Tom
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=4B74689A.9060008@fearnside-systems.co.uk \
--to=kevin.morfitt@fearnside-systems.co.uk \
--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