From: Greg KH <gregkh@linuxfoundation.org>
To: Sanjeev Sharma <sanjeev_sharma@mentor.com>
Cc: devel@driverdev.osuosl.org, waydi1@gmail.com,
swetland@google.com, linux-kernel@vger.kernel.org,
daniel@ffwll.ch
Subject: Re: [PATCH] staging: android: Fixed missing blank line
Date: Fri, 18 Jul 2014 16:16:10 -0700 [thread overview]
Message-ID: <20140718231610.GA29987@kroah.com> (raw)
In-Reply-To: <1405658874-24448-1-git-send-email-sanjeev_sharma@mentor.com>
On Fri, Jul 18, 2014 at 10:17:54AM +0530, Sanjeev Sharma wrote:
> This patch will add an blank line after
> declaration reported by checkpatch.pl script.
>
> Signed-off-by: Sanjeev Sharma <Sanjeev_Sharma@mentor.com>
> ---
> drivers/staging/android/sw_sync.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/staging/android/sw_sync.c b/drivers/staging/android/sw_sync.c
> index a76db3f..863d4b1 100644
> --- a/drivers/staging/android/sw_sync.c
> +++ b/drivers/staging/android/sw_sync.c
> @@ -97,6 +97,7 @@ static void sw_sync_pt_value_str(struct sync_pt *sync_pt,
> char *str, int size)
> {
> struct sw_sync_pt *pt = (struct sw_sync_pt *)sync_pt;
> +
> snprintf(str, size, "%d", pt->value);
> }
>
> @@ -156,6 +157,7 @@ static int sw_sync_open(struct inode *inode, struct file *file)
> static int sw_sync_release(struct inode *inode, struct file *file)
> {
> struct sw_sync_timeline *obj = file->private_data;
> +
> sync_timeline_destroy(&obj->obj);
> return 0;
> }
I already applied a previous version of this patch, with your gmail
address :(
next prev parent reply other threads:[~2014-07-18 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 4:47 [PATCH] staging: android: Fixed missing blank line Sanjeev Sharma
2014-07-18 23:16 ` Greg KH [this message]
2014-07-23 10:08 ` Sharma, Sanjeev
2014-07-23 15:25 ` Greg KH
2014-07-28 5:14 ` Sharma, Sanjeev
-- strict thread matches above, loose matches on Subject: below --
2014-07-17 7:18 sanjeev sharma
2014-07-17 7:28 ` Dan Carpenter
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=20140718231610.GA29987@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjeev_sharma@mentor.com \
--cc=swetland@google.com \
--cc=waydi1@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.