public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: DaeSeok Youn <daeseok.youn@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Brian Swetland <swetland@google.com>,
	John Stultz <john.stultz@linaro.org>,
	Rebecca Zavin <rebecca@android.com>,
	ccross@android.com, ohaugan@codeaurora.org,
	Rom Lemarchand <romlem@google.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Resend PATCH] staging : ion : Fix some checkpatch warnings and an error
Date: Mon, 10 Feb 2014 16:20:24 -0800	[thread overview]
Message-ID: <1392078024.2507.34.camel@joe-AO722> (raw)
In-Reply-To: <CAHb8M2DZHv7qsnt8RxAKyycMptyvKbfZcCtwV4juTs4jRp_z-A@mail.gmail.com>

On Tue, 2014-02-11 at 09:11 +0900, DaeSeok Youn wrote:
> Hi,

Hello.

> Thanks for review.
> If I send this patch again, i will use a subject as you comment.

Thanks.

> And alignment issue, my patch line seems to be same with your example.

You took out a space from the line with the function pointer
but not from the subsequent lines of the arguments.

> >> diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c
> > []
> >> @@ -55,7 +55,7 @@ struct ion_device {
> >>       struct mutex buffer_lock;
> >>       struct rw_semaphore lock;
> >>       struct plist_head heaps;
> >> -     long (*custom_ioctl) (struct ion_client *client, unsigned int cmd,
> >> +     long (*custom_ioctl)(struct ion_client *client, unsigned int cmd,
> >>                             unsigned long arg);
> >
> > Please realign the arguments to the open parenthesis like:
> >
> >         long (*custom_ioctl)(struct ion_client *client, unsigned int cmd,
> >                              unsigned long arg);

Your patch has:

	long (*custom_ioctl)(struct ion_client *client, unsigned int cmd,
			      unsigned long arg);

it should be:

	long (*custom_ioctl)(struct ion_client *client, unsigned int cmd,
			     unsigned long arg);

with the "unsigned long arg" aligned immediately after
the open parenthesis of the function arguments.

(under the "s" of struct, not the first "t" of struct)




  reply	other threads:[~2014-02-11  0:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 11:25 [Resend PATCH] staging : ion : Fix some checkpatch warnings and an error Daeseok Youn
2014-02-10 16:33 ` Joe Perches
2014-02-11  0:11   ` DaeSeok Youn
2014-02-11  0:20     ` Joe Perches [this message]
2014-02-11  1:02       ` DaeSeok Youn

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=1392078024.2507.34.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=ccross@android.com \
    --cc=daeseok.youn@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ohaugan@codeaurora.org \
    --cc=rebecca@android.com \
    --cc=romlem@google.com \
    --cc=swetland@google.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