From: Greg KH <gregkh@linuxfoundation.org>
To: Bopamo Osaisai <bopamo@gmail.com>
Cc: arve@android.com, riandrews@android.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: android: Fix brace coding style warning in sync_debug.c
Date: Sun, 7 Feb 2016 14:57:24 -0800 [thread overview]
Message-ID: <20160207225724.GD8463@kroah.com> (raw)
In-Reply-To: <1453858293-4634-1-git-send-email-bopamo@gmail.com>
On Tue, Jan 26, 2016 at 05:31:33PM -0800, Bopamo Osaisai wrote:
> This is a patch to the sync_debug.c file that rectifies a brace warning
> that was found with the checkpatch.pl tool
>
> Signed-off-by: Bopamo Osaisai <bopamo@gmail.com>
> ---
> drivers/staging/android/sync_debug.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/android/sync_debug.c b/drivers/staging/android/sync_debug.c
> index f45d13c..02a1649 100644
> --- a/drivers/staging/android/sync_debug.c
> +++ b/drivers/staging/android/sync_debug.c
> @@ -158,9 +158,8 @@ static void sync_print_fence(struct seq_file *s, struct sync_fence *fence)
> seq_printf(s, "[%p] %s: %s\n", fence, fence->name,
> sync_status_str(atomic_read(&fence->status)));
>
> - for (i = 0; i < fence->num_fences; ++i) {
> + for (i = 0; i < fence->num_fences; ++i)
> sync_print_pt(s, fence->cbs[i].sync_pt, true);
> - }
>
> spin_lock_irqsave(&fence->wq.lock, flags);
> list_for_each_entry(pos, &fence->wq.task_list, task_list) {
> --
> 2.7.0
Someone else already sent this in before you :(
next prev parent reply other threads:[~2016-02-07 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 1:31 [PATCH] Staging: android: Fix brace coding style warning in sync_debug.c Bopamo Osaisai
2016-02-07 22:57 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-08 17:15 Bopamo Osaisai
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=20160207225724.GD8463@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=bopamo@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.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.