From: Joe Perches <joe@perches.com>
To: becher.jannik@gmail.com, Andrey Utkin <andrey_utkin@fastmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: wlan-ng: fixed a coding style issue
Date: Thu, 22 Sep 2016 14:03:44 -0700 [thread overview]
Message-ID: <1474578224.8253.30.camel@perches.com> (raw)
In-Reply-To: <20160922205218.ndkbjkcyfnfs22jz@breaker.fritz.box>
On Thu, 2016-09-22 at 22:52 +0200, becher.jannik@gmail.com wrote:
> I always wondered why I shouldn't make more than one change in a patch,
> but in all talks I watched they said that it's easier for them to merge
> small patches.
>
> So you think I should make one "big" patch and resend it?
Make separate patches for each "type" of change.
Here it would be removing unnecessary space before all
casts in the same file or for all specific driver files.
next prev parent reply other threads:[~2016-09-22 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 19:11 [PATCH] drivers: wlan-ng: fixed a coding style issue Jannik Becher
2016-09-22 20:32 ` Andrey Utkin
2016-09-22 20:52 ` becher.jannik
2016-09-22 21:03 ` Joe Perches [this message]
2016-09-22 21:14 ` Andrey Utkin
-- strict thread matches above, loose matches on Subject: below --
2016-09-22 21:56 Jannik Becher
2016-09-22 22:05 ` Joe Perches
2016-09-22 22:39 ` becher.jannik
2016-09-22 22:52 ` Joe Perches
2016-09-22 18:01 Jannik Becher
2016-09-22 18:27 ` Joe Perches
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=1474578224.8253.30.camel@perches.com \
--to=joe@perches.com \
--cc=andrey_utkin@fastmail.com \
--cc=becher.jannik@gmail.com \
--cc=devel@driverdev.osuosl.org \
--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