From: Joe Perches <joe@perches.com>
To: Greg Donald <gdonald@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: staging: rtl8821ae: Fix spaces required around that '?' errors
Date: Mon, 25 Aug 2014 06:56:04 -0700 [thread overview]
Message-ID: <1408974964.20683.50.camel@joe-AO725> (raw)
In-Reply-To: <CAO+WgCY8Ugv17WMEe0TEn0ruf9HAF=uNZ12OKjZmehsO6kvZ1Q@mail.gmail.com>
On Mon, 2014-08-25 at 08:51 -0500, Greg Donald wrote:
> On Mon, Aug 25, 2014 at 8:15 AM, Joe Perches <joe@perches.com> wrote:
> > On Mon, 2014-08-25 at 06:35 -0500, Greg Donald wrote:
> >> Fix checkpatch.pl spaces required around that '?' errors
> >
> > It'd be better to convert all parts of the
> > ternary at the same time.
>
> Wouldn't "at the same time" be in direct conflict with the "only do
> one thing per patch" rule?
No because these are both whitespace changes
around a ternary.
As far as I'm concerned, a single patch to do
all horizontal whitespace corrections at the
same time is just fine.
Just make sure to check your changes don't modify
anything with git diff -w and scripts/objdiff.
> > A subsequent change might be to remove the unnecessary
> > parentheses like:
> >
> > force_exec ? "force to" : "", dec_bt_pwr ? "ON" : "OFF");
>
> I understand. It's very likely I'll submit such a patch in the future.
>
> I'm currently attempting to keep my cleanups to a single error/warning
> type so I get as much done as possible per patch while also keeping
> the patch easy to review. Is this wrong?
No, it's the appropriate thing to do.
next prev parent reply other threads:[~2014-08-25 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 11:35 Greg Donald
2014-08-25 13:15 ` Joe Perches
2014-08-25 13:51 ` Greg Donald
2014-08-25 13:56 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-24 23:34 [PATCH] drivers: staging: rtl8821ae: Fix spaces required around that '<' errors Greg Donald
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=1408974964.20683.50.camel@joe-AO725 \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gdonald@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®