From: Ian Abbott <abbotti@mev.co.uk>
To: Philippe Loctaux <phil@philippeloctaux.com>, gregkh@linuxfoundation.org
Cc: hsweeten@visionengravers.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: mite: added spaces around | and *
Date: Tue, 23 Feb 2016 16:48:23 +0000 [thread overview]
Message-ID: <56CC8D57.7000004@mev.co.uk> (raw)
In-Reply-To: <1456184291-30665-1-git-send-email-phil@philippeloctaux.com>
On 22/02/16 23:38, Philippe Loctaux wrote:
> Added spaces around | and *, fixing 2 checkpatch checks.
>
> Signed-off-by: Philippe Loctaux <phil@philippeloctaux.com>
> ---
> drivers/staging/comedi/drivers/mite.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
[snip]
> @@ -216,7 +216,7 @@ EXPORT_SYMBOL_GPL(mite_free_ring);
> struct mite_channel *mite_request_channel_in_range(struct mite_struct *mite,
> struct
> mite_dma_descriptor_ring
> - *ring, unsigned min_channel,
> + * ring, unsigned min_channel,
> unsigned max_channel)
Actually, that one looks like a false positive by the checkpatch tool.
I'd expect no space after that '*'. checkpatch has probably got
confused by the line-break before the '*'.
It looks a bit ugly anyway. It would look better if there was a
line-break before the function name, the same as in
"drivers/staging/comedi/drivers/mite.h":
struct mite_channel *
mite_request_channel_in_range(struct mite_struct *mite,
struct mite_dma_descriptor_ring *ring,
unsigned min_channel, unsigned max_channel)
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2016-02-23 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 23:38 Philippe Loctaux
2016-02-23 0:37 ` Joe Perches
2016-02-23 11:07 ` Ian Abbott
2016-02-23 12:38 ` Philippe Loctaux
2016-02-23 16:39 ` Ian Abbott
2016-02-23 16:48 ` Ian Abbott [this message]
2016-02-23 21:47 ` Philippe Loctaux
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=56CC8D57.7000004@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@philippeloctaux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome