From: Greg KH <gregkh@linuxfoundation.org>
To: Murilo Opsfelder Araujo <mopsfelder@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
ydroneaud@opteya.com, waydi1@gmail.com, daniel@ffwll.ch,
maarten.lankhorst@canonical.com, sumit.semwal@linaro.org
Subject: Re: [PATCH] Staging: android: sw_sync.c: fix missing blank line after declaration
Date: Wed, 30 Jul 2014 17:17:40 -0700 [thread overview]
Message-ID: <20140731001740.GA31573@kroah.com> (raw)
In-Reply-To: <1406587103-5784-1-git-send-email-mopsfelder@gmail.com>
On Mon, Jul 28, 2014 at 07:38:23PM -0300, Murilo Opsfelder Araujo wrote:
> Fix coding style issue.
>
> Signed-off-by: Murilo Opsfelder Araujo <mopsfelder@gmail.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;
> }
Does not apply to my tree at all :(
next prev parent reply other threads:[~2014-07-31 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 22:38 [PATCH] Staging: android: sw_sync.c: fix missing blank line after declaration Murilo Opsfelder Araujo
2014-07-31 0:17 ` Greg KH [this message]
2014-07-31 11:44 ` Murilo Opsfelder Araujo
2014-07-31 13:00 ` Yann Droneaud
2014-07-31 13:30 ` Dan Carpenter
2014-07-31 13:44 ` Yann Droneaud
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=20140731001740.GA31573@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=mopsfelder@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=waydi1@gmail.com \
--cc=ydroneaud@opteya.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.