From: Varka Bhadram <varkabhadram@gmail•com>
To: Florian Fainelli <f.fainelli@gmail•com>
Cc: netdev <netdev@vger•kernel.org>, Varka Bhadram <varkab@cdac•in>,
David Miller <davem@davemloft•net>,
linux-zigbee-devel@lists•sourceforge.net,
Joe Perches <joe@perches•com>
Subject: Re: [Linux-zigbee-devel] [PATCH net-next v3] 6lowpan: mac802154: fix coding style issues
Date: Wed, 02 Jul 2014 09:58:30 +0530 [thread overview]
Message-ID: <53B38A6E.2000603@gmail.com> (raw)
In-Reply-To: <CAGVrzcYc9u2TAxhb8vPOevLYiZUsOyEcUAbxZ4aLrns3Vt97yw@mail.gmail.com>
Hi Florian,
On 07/02/2014 09:50 AM, Florian Fainelli wrote:
> Hi,
>
> 2014-07-01 20:31 GMT-07:00 Varka Bhadram <varkabhadram@gmail•com>:
>> This patch fixed the coding style issues reported by checkpatch.pl
>>
>> following issues fixed:
>> CHECK: Alignment should match open parenthesis
> It seems to me like checkpatch.pl should have a special case for
> networking code and that specific condition because fixing things to
> make checkpatch.pl happy seems not to agree with the general coding
> style recommended and enforced in the networking code.
>
> I just saw that new warning added popping up on a bunch of drivers
> that were properly fixed to match the networking coding style before
> submission.
Sorry, I didn't get what you are saying...
Is there any thing to be fixed in the patch ?
--
Varka Bhadram
next prev parent reply other threads:[~2014-07-02 4:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 3:31 [PATCH net-next v3] 6lowpan: mac802154: fix coding style issues Varka Bhadram
2014-07-02 4:20 ` [Linux-zigbee-devel] " Florian Fainelli
2014-07-02 4:28 ` Varka Bhadram [this message]
2014-07-02 4:38 ` Florian Fainelli
2014-07-02 4:40 ` Joe Perches
2014-07-02 4:49 ` Florian Fainelli
2014-07-02 4:58 ` Joe Perches
2014-07-02 5:07 ` Florian Fainelli
2014-07-02 5:14 ` David Miller
2014-07-08 3:55 ` David Miller
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=53B38A6E.2000603@gmail.com \
--to=varkabhadram@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=joe@perches$(echo .)com \
--cc=linux-zigbee-devel@lists$(echo .)sourceforge.net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=varkab@cdac$(echo .)in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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