All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Kirtika Ruchandani <kirtika.ruchandani@gmail.com>,
	ruchandani.tina@gmail.com, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/3] nl80211: Fix checkpatch warnings
Date: Tue, 31 May 2016 12:29:42 +0200	[thread overview]
Message-ID: <1464690582.3076.21.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGRGNgXuE3smks0pYoMQ5NxqjUN0PJ7i6LgBDjkq_uWyfPHQkA@mail.gmail.com> (sfid-20160530_023028_641313_76E294B4)

On Mon, 2016-05-30 at 10:30 +1000, Julian Calaby wrote:
> Hi All,
> 
> On Sun, May 29, 2016 at 1:30 PM, Kirtika Ruchandani
> <kirtika.ruchandani@gmail.com> wrote:
> > 
> > This patch fixes the following checkpatch.pl warnings about
> > comments in nl80211.c :
> > - networking block comments don't use an empty '/*' line
> > - block comments use a trailing '*/' on a separate line
> > 
> > Signed-off-by: Kirtika Ruchandani <kirtika.ruchandani@gmail.com>
> The change and logic behind it are sound, so it gets my:
> 
> Reviewed-by: Julian Calaby <julian.calaby@gmail.com>
> 
> however I'm concerned that this file is a deliberate exception to the
> networking comment rules.
> 

It's kinda mixed, I never really enforced one style or the other ...
I'm kinda taking both now, with a slight preference towards the
networking style perhaps (to please davem :) )

That said, in general I'm not really sure of the value of all of these
patches - perhaps the kcalloc() one makes sense, not for checkpatch
reasons but rather for size limit/integer overflow reasons, and the
ether address assign for general readability, but overall ...

I'll have to make up my mind :)

johannes

  reply	other threads:[~2016-05-31 10:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29  3:30 [PATCH 0/3] nl80211: Fix checkpatch.pl issues Kirtika Ruchandani
2016-05-29  3:30 ` [PATCH 1/3] nl80211: Fix checkpatch warnings Kirtika Ruchandani
2016-05-29  3:30   ` Kirtika Ruchandani
2016-05-30  0:30   ` Julian Calaby
2016-05-31 10:29     ` Johannes Berg [this message]
2016-05-29  3:31 ` [PATCH 2/3] nl80211: Fix checkpatch warnings about blank lines Kirtika Ruchandani
2016-05-30  0:31   ` Julian Calaby
2016-05-30  0:31     ` Julian Calaby
2016-05-29  3:31 ` [PATCH 3/3] nl80211: Various checkpatch.pl fixes Kirtika Ruchandani
2016-05-30  0:35   ` Julian Calaby
2016-05-30  0:40     ` Kirtika Ruchandani
2016-05-30  0:44       ` Kirtika Ruchandani
2016-05-30  0:47         ` Julian Calaby
2016-05-30  0:47           ` Julian Calaby

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=1464690582.3076.21.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=julian.calaby@gmail.com \
    --cc=kirtika.ruchandani@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ruchandani.tina@gmail.com \
    /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.