From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc: Fix CamelCase checkpatch warnings
Date: Fri, 16 Aug 2013 14:43:31 +0530 [thread overview]
Message-ID: <520DED3B.2070602@freescale.com> (raw)
In-Reply-To: <593AEF6C47F46446852B067021A273D6D9828F36@MUCSE039.lantiq.com>
On 08/16/2013 02:23 PM, thomas.langer at lantiq.com wrote:
> Hello Prabhakar,
>
> Prabhakar Kushwaha wrote on 2013-08-16:
>> 85xx, 86xx PowerPC folders have code variables with CamelCase naming
>> conventions. because of this code checkpatch script generates "WARNING:
>> Avoid CamelCase".
>>
>> This patch set Convert variables name to normal naming convention and
>> modify board, driver files with updated new
>> - [PATCH 1/2] powerpc: Fix CamelCase checkpatch warnings
>> - [PATCH 2/2] board: Update variable names as per new the structures
>>
> I think you have to fold both patches together to have the change bisectable!
> Otherwise your board code will not compile after applying only the first patch.
>
>
Thanks Thomas,
I will merge both the patches.
Regards,
Prabhakar
prev parent reply other threads:[~2013-08-16 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 7:26 [U-Boot] [PATCH] powerpc: Fix CamelCase checkpatch warnings Prabhakar Kushwaha
2013-08-16 8:53 ` thomas.langer at lantiq.com
2013-08-16 9:13 ` Prabhakar Kushwaha [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=520DED3B.2070602@freescale.com \
--to=prabhakar@freescale.com \
--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.