From: Greg KH <gregkh@linuxfoundation.org>
To: Robin Krahl <robin.krahl@ireas.org>
Cc: devel@driverdev.osuosl.org, "Arve Hjønnevåg" <arve@android.com>,
"Riley Andrews" <riandrews@android.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] staging: android: sync_debug.c: remove unnecessary braces
Date: Sun, 7 Feb 2016 14:56:43 -0800 [thread overview]
Message-ID: <20160207225643.GA8463@kroah.com> (raw)
In-Reply-To: <20160119112941.GA1766@spectator>
On Tue, Jan 19, 2016 at 12:29:41PM +0100, Robin Krahl wrote:
> Remove unnecessary braces {} around a single statement within a for loop.
> Indicated by checkpatch.
>
> Signed-off-by: Robin Krahl <robin.krahl@ireas.org>
> ---
> 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.5.0
>
Someone sent a fixed up patch before this one :(
prev parent reply other threads:[~2016-02-07 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:29 [PATCH RESEND] staging: android: sync_debug.c: remove unnecessary braces Robin Krahl
2016-02-07 22:56 ` Greg KH [this message]
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=20160207225643.GA8463@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=robin.krahl@ireas.org \
/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;
as well as URLs for NNTP newsgroup(s).