From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marcus Wolf <marcus.wolf@wolf-entwicklungen.de>
Cc: gregkh@linuxfoundation.org, Derek Robson <robsonde@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] staging: pi433: - style fix, space before tabs
Date: Mon, 24 Jul 2017 10:48:58 +0300 [thread overview]
Message-ID: <20170724074858.q7hsqlk5et65kegl@mwanda> (raw)
In-Reply-To: <403797028.18523.1500713304938@ox.hosteurope.de>
On Sat, Jul 22, 2017 at 10:48:24AM +0200, Marcus Wolf wrote:
> Reviewed-by: Marcus Wolf <linux@wolf-entwicklungen.de>
>
> >From my point of view, the rearrangement of the block of SET_CHECKED reduces the
> readability a lot. I like same stuff to be aligned (all brakets below each other
> as a column, all spi->dev below each other and so on) But if it is necessary to
> fullfill the rules, we have to do it the new way.
It's not necessary. The rule is just complaining about this:
SET_CHECKED(rf69_set_bandwidth (dev->spi, rx_cfg->bw_mantisse, rx_cfg->bw_exponent));
^
There is a space after the 'h' character. The old code has
"[space][tab][tab][space](dev->spi,..." it should be:
"[tab][tab][space](dev->spi, ..."
Also the rules are there to improve readability. Sometimes they're
debatable but if they make readability worse, then we can ignore the
rules.
regards,
dan carpenter
prev parent reply other threads:[~2017-07-24 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 3:51 [PATCH 2/3] staging: pi433: - style fix, space before tabs Derek Robson
2017-07-22 8:48 ` Marcus Wolf
2017-07-24 7:48 ` Dan Carpenter [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=20170724074858.q7hsqlk5et65kegl@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.wolf@wolf-entwicklungen.de \
--cc=robsonde@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox