mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Ioana Antoche <ioana.antoche@gmail.com>,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nits: fix several coding style warnings
Date: Sun, 08 Mar 2015 15:18:45 -0700	[thread overview]
Message-ID: <1425853125.2745.4.camel@perches.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1503082313150.7485@axis700.grange>

On Sun, 2015-03-08 at 23:14 +0100, Guennadi Liakhovetski wrote:
> On Sun, 8 Mar 2015, Ioana Antoche wrote:
> > Fix checkpatch.pl warnings such as:
> > * missing blank line after declarations
> > * line over 80 characters
[]
> > @@ -298,8 +299,7 @@ static struct device *next_device(struct klist_iter *i)
> >   * count in the supplied callback.
> >   */
> >  int bus_for_each_dev(struct bus_type *bus, struct device *start,
> > -		     void *data, int (*fn)(struct device *, void *))
> > -{
> > +		     void *data, int (*fn)(struct device *, void *)) {
> 
> Really curious: is this change (and a similar one below) really fixing a 
> style violation?

Nope.

The "for_each" use in a function name confuses checkpatch.
Normally, those are macros.

> > @@ -448,8 +449,7 @@ static struct device_driver *next_driver(struct klist_iter *i)
> >   * so it doesn't disappear before returning to the caller.
> >   */
> >  int bus_for_each_drv(struct bus_type *bus, struct device_driver *start,
> > -		     void *data, int (*fn)(struct device_driver *, void *))
> > -{
> > +		     void *data, int (*fn)(struct device_driver *, void *)) {




      reply	other threads:[~2015-03-08 22:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 10:53 Ioana Antoche
2015-03-08 12:39 ` Greg KH
2015-03-08 16:20   ` Daniel Baluta
2015-03-08 22:14 ` Guennadi Liakhovetski
2015-03-08 22:18   ` Joe Perches [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=1425853125.2745.4.camel@perches.com \
    --to=joe@perches.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=ioana.antoche@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®