From: Joe Perches <joe@perches.com>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: gregkh@linuxfoundation.org, swetland@google.com,
john.stultz@linaro.org, rebecca@android.com, ccross@android.com,
ohaugan@codeaurora.org, romlem@google.com,
linux-kernel@vger.kernel.org, dan.carpenter@oracle.com
Subject: Re: [Resend PATCH] staging : ion : Fix some checkpatch warnings and an error
Date: Mon, 10 Feb 2014 08:33:38 -0800 [thread overview]
Message-ID: <1392050018.2507.6.camel@joe-AO722> (raw)
In-Reply-To: <1861074.WmPcbRBdNV@daeseok-laptop.cloud.net>
On Mon, 2014-02-10 at 20:25 +0900, Daeseok Youn wrote:
> Warning:
> - Unnecessary space after function pointer name
> - quoted string split across lines
>
> Error:
> - return is not a function, parentheses are not required
Hi.
checkpatch issuing either an ERROR or WARNING isn't
really relevant to the subject.
This isn't really a resend. It's a different version
and so the subject should not say "Resend". Ideally,
you send this with a subject like:
[PATCH V2] staging: ion: Whitespace neatening
and if needed again:
[PATCH V3] staging: ion: Whitespace neatening
etc...
and below:
> 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);
> diff --git a/drivers/staging/android/ion/ion_priv.h b/drivers/staging/android/ion/ion_priv.h
[]
> @@ -100,18 +100,18 @@ void ion_buffer_destroy(struct ion_buffer *buffer);
> * map_dma and map_kernel return pointer on success, ERR_PTR on error.
> */
> struct ion_heap_ops {
> - int (*allocate) (struct ion_heap *heap,
> + int (*allocate)(struct ion_heap *heap,
> struct ion_buffer *buffer, unsigned long len,
> unsigned long align, unsigned long flags);
realignment here too
etc.
next prev parent reply other threads:[~2014-02-10 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 11:25 Daeseok Youn
2014-02-10 16:33 ` Joe Perches [this message]
2014-02-11 0:11 ` DaeSeok Youn
2014-02-11 0:20 ` Joe Perches
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=1392050018.2507.6.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
all inboxes | Powered by JetHome®