public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: ching2048@areca.com.tw
Cc: linux-scsi@vger.kernel.org
Subject: Re: [SCSI] arcmsr: Support Areca new SATA Raid Adapter ARC1214/1224/1264/1284
Date: Thu, 29 Aug 2013 15:01:41 +0300	[thread overview]
Message-ID: <20130829120141.GI19256@mwanda> (raw)
In-Reply-To: <20130828154848.GA571@elgon.mountain>

One tool for breaking patches up is "git citool" highlight what you want
to add to the patch and then right click and select "stage lines for
commit".

So for example let's go through the changes to
drivers/scsi/arcmsr/arcmsr.h.  These should be broken up into multiple
patches with the easiest whitespace patches first.

The original patch adds 520 lines of code (I'm looking at the plus marks
in git show 17628f3a062b | diffstat).  Out of those 392 line are pure
white space changes such as tabs or indents.  9 lines are adding
parenthesis around macros.  4 lines are changing int32_t to uint32_t.
It's not clear if there was a signedness bug in the original code or if
this is purely cosmetic.  That should be mentioned in the changelog.
The remaining 115 lines are related to the new feature.  So this should
be a series of patches.

[patch 1/4] whitespace (this is the largest patch in the series).
[patch 2/4] add parenthesis
[patch 3/4] change signed to unsigned
[patch 4/4] add feature (this would touch other the other files as well)

The first 3 patches are trivial to review and then the last one is much
smaller and easier to review than when everything was mixed together.

regards,
dan carpenter

      parent reply	other threads:[~2013-08-29 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 15:48 [SCSI] arcmsr: Support Areca new SATA Raid Adapter ARC1214/1224/1264/1284 Dan Carpenter
2013-08-28 16:25 ` James Bottomley
2013-08-29 12:01 ` 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=20130829120141.GI19256@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=ching2048@areca.com.tw \
    --cc=linux-scsi@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