From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Tobias Nießen" <tobias.niessen@stud.uni-hannover.de>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
Sabrina Gaube <sabrina-gaube@web.de>,
linux-kernel@vger.kernel.org, linux-kernel@i4.cs.fau.de
Subject: Re: [PATCH 1/2] staging: rts5208: Rewrite redundant if statement to improve code style
Date: Wed, 26 Jun 2019 17:56:36 +0300 [thread overview]
Message-ID: <20190626145636.GG28859@kadam> (raw)
In-Reply-To: <20190626142857.30155-2-tobias.niessen@stud.uni-hannover.de>
Both these patches seem fine.
On Wed, Jun 26, 2019 at 04:28:56PM +0200, Tobias Nießen wrote:
> This commit uses the fact that
>
> if (a) {
> if (b) {
> ...
> }
> }
>
> can instead be written as
>
> if (a && b) {
> ...
> }
>
> without any change in behavior, allowing to decrease the indentation
> of the contained code block and thus reducing the average line length.
>
> Signed-off-by: Tobias Nießen <tobias.niessen@stud.uni-hannover.de>
> Signed-off-by: Sabrina Gaube <sabrina-gaube@web.de>
Signed-off-by is like signing a legal document that you didn't put any
of SCO's secret UNIXWARE source code into your patch or do other illegal
activities. Everyone who handles a patch is supposed to Sign it.
It's weird to see Sabrina randomly signing your patches. Probably there
is a more appropriate kind of tag to use as well or instead such as
Co-Developed-by, Reviewed-by or Suggested-by.
regards,
dan carpenter
next prev parent reply other threads:[~2019-06-26 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 14:28 staging: rts5208: Two patches to improve code style Tobias Nießen
2019-06-26 14:28 ` [PATCH 1/2] staging: rts5208: Rewrite redundant if statement " Tobias Nießen
2019-06-26 14:56 ` Dan Carpenter [this message]
2019-06-30 14:12 ` Tobias Nießen
2019-07-17 8:48 ` Dan Carpenter
2019-06-26 17:41 ` Joe Perches
2019-06-26 14:28 ` [PATCH 2/2] staging: rts5208: Simplify boolean expression " Tobias Nießen
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=20190626145636.GG28859@kadam \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sabrina-gaube@web.de \
--cc=tobias.niessen@stud.uni-hannover.de \
/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