From: Johan Hovold <johan@kernel.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: simran singhal <singhalsimran0@gmail.com>,
johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2 3/6] staging: greybus: Remove unnecessary braces
Date: Tue, 21 Feb 2017 14:44:36 +0100 [thread overview]
Message-ID: <20170221134436.GB10245@localhost> (raw)
In-Reply-To: <alpine.DEB.2.20.1702211420300.3121@hadrien>
On Tue, Feb 21, 2017 at 02:20:50PM +0100, Julia Lawall wrote:
>
>
> On Tue, 21 Feb 2017, simran singhal wrote:
>
> > This patch removes braces for single statement blocks. The warning
> > was detected using checkpatch.pl.
> > Coccinelle was used to make the change.
> >
> > @@
> > expression e,e1;
> > @@
> > - if (e) {
> > + if (e)
> > e1;
> > - }
> >
> > Signed-off-by: simran singhal <singhalsimran0@gmail.com>
>
> Acked-by: Julia Lawall <julia.lawall@lip6.fr>
I do not think this patch should be merged.
Note that all of the braces you are removing are for single statements
that span multiple lines, and that is precisely why the braces were
added in the first place. Having braces for such statements often
increase readability even if they are not mandated by the coding
standard.
So I suggest this patch is dropped.
Thanks,
Johan
next prev parent reply other threads:[~2017-02-21 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 13:15 [PATCH v2 3/6] staging: greybus: Remove unnecessary braces simran singhal
2017-02-21 13:20 ` [Outreachy kernel] " Julia Lawall
2017-02-21 13:44 ` Johan Hovold [this message]
2017-02-21 13:46 ` [greybus-dev] " Alex Elder
2017-02-21 13:21 ` Julia Lawall
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=20170221134436.GB10245@localhost \
--to=johan@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=singhalsimran0@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.