From: Dan Carpenter <dan.carpenter@oracle.com>
To: Masaru Nomura <massa.nomura@gmail.com>
Cc: devel@driverdev.osuosl.org, Lidza Louina <lidza.louina@gmail.com>,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 3/4] staging: dgnc: dgnc_neo: Fix conditional part of if statement
Date: Sun, 18 May 2014 00:23:54 +0300 [thread overview]
Message-ID: <20140517212353.GH15585@mwanda> (raw)
In-Reply-To: <CAAvxhqB0ACdZy3q6zbAd-JAtxSSojPYyQq3ZKTfdyisN+e5HjA@mail.gmail.com>
On Sat, May 17, 2014 at 10:14:52PM +0100, Masaru Nomura wrote:
> > Also just fold this patch and [patch 2/4] together into one patch. We
> > don't need two patches to fix one if statement.
> >
> > The one thing per patch rule is a bit tricky. It means that you have to
> > say which one thing you are fixing. Don't say "I am fixing three
> > things." Say "I am fixing one if statement".
>
> So in this case, do you think I could fold all four patches into one?
No. That would be more than one thing per patch. It looks like this:
[patch 1/3] staging: dgnc: dgnc_neo: put else statements on the right line
[patch 2/3] staging: dgnc: dgnc_neo: clean up ugly one very ugly condition
[patch 3/3] staging: dgnc: dgnc_neo: remove extra curly braces
Each patch does one thing. Cleaning up the whole file is too big so it
doesn't count as doing one thing only.
> As I just worked on the 'same' if statements and divided them into
> four patches, this could be the case. (but I'm not sure yet...)
>
> Also, should I put v[number] for the modified patches?
> Say [PATCH v2] staging: ...
Yes.
regards,
dan carpenter
next prev parent reply other threads:[~2014-05-17 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 16:30 [PATCH 0/4] Fix coding style of if statement Masaru Nomura
2014-05-17 16:30 ` [PATCH 1/4] staging: dgnc: Fix indenting of if-else statement Masaru Nomura
2014-05-17 16:30 ` [PATCH 2/4] staging: dgnc: dgnc_neo: Fix indenting of if statement Masaru Nomura
2014-05-17 16:30 ` [PATCH 3/4] staging: dgnc: dgnc_neo: Fix conditional part " Masaru Nomura
2014-05-17 19:39 ` Dan Carpenter
2014-05-17 21:14 ` Masaru Nomura
2014-05-17 21:23 ` Dan Carpenter [this message]
2014-05-17 16:30 ` [PATCH 4/4] staging: dgnc: Remove unnecessary braces Masaru Nomura
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=20140517212353.GH15585@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=massa.nomura@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.