From: Boaz Harrosh <bharrosh@panasas.com>
To: Ke Wei <kewei.mv@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-scsi@vger.kernel.org,
James.Bottomley@hansenpartnership.com, qswang@marvell.com,
jfeng@marvell.com, qzhao@marvell.com, lil@marvell.com,
saeed.bishara@gmail.com, kewei@marvell.com
Subject: Re: [PATCH] mvsas: convert from rough draft to working driver
Date: Tue, 04 Mar 2008 20:59:35 +0200 [thread overview]
Message-ID: <47CD9C17.3090508@panasas.com> (raw)
In-Reply-To: <20080224114806.GA7908@ubuntu.domain>
On Sun, Feb 24 2008 at 13:48 +0200, Ke Wei <kewei.mv@gmail.com> wrote:
> On Sat, Feb 23, 2008 at 11:28:50AM -0500, Jeff Garzik wrote:
>> Ke Wei wrote:
>>> Convert rough draft Marvell 6440 driver to a working driver.
>>> Added support for SAS and SATA devices, hotplug, wide port, and expanders.
>>> This patch is based on:
>>> branch 'mvsas' of
>>> git.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
>> Yay! Perfect patch: good tech content, applyable to #mvsas, and the
>> most important part, the driver works :)
>>
>> One minor (though important) detail: may we assume this patch has the
>> same Signed-off-by as previous patches?
>>
>
> Oah, I have no idea how to diff between the previous 5th commit and
> current to use git-format-patch command, so I had to use git-diff to
> create patch. As a result, I format to place my Signed-off-by when
> sending email.
> Jeff, Do you have a good suggestion? Thank you for your help.
Do you mean you have 5 patches in git that you want to send as
one patch to the list?
- if so then lets say you are in branch my_branch based off master
and it has your 5 patches. And lets say you want to keep your
original 5 patch, but have an alternative one patch for them all.
- $ git-checkout -b my_one_patch my_branch
- $ git-rebase--interactive master
- At this stage you will get your $GIT_EDITOR with a list of your
5 patches like:
pick xxxxxxx patch one
pick yyyyyyy patch two
...
edit the "pick" at start of line to "squash" to all but the first
patch. Save and exit the editor.
- git will ask you to edit the commit message of the now combined patch,
in an editor, do so. Verify you have a Signed-off-by:, save and exit.
- Rebase should finish cleanly, leaving you with one patch that can then
be sent with $ git-format-patch -1.
- If you do $ git-diff my_one_patch my_branch
they are identical
- But $ git-log my_one_patch
will only have one patch following master
Any re-edits of your git history git-rebase--interactive is your
friend.
>
> Now,
> Signed-off-by: Ke Wei <kewei@marvell.com>
>
>> Thanks and have a good weekend,
>>
>> Jeff
>>
> -
Boaz
prev parent reply other threads:[~2008-03-04 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 13:15 [PATCH] mvsas: convert from rough draft to working driver Ke Wei
2008-02-23 16:28 ` Jeff Garzik
2008-02-24 11:48 ` Ke Wei
2008-02-25 23:11 ` Jeff Garzik
2008-03-04 18:59 ` Boaz Harrosh [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=47CD9C17.3090508@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jeff@garzik.org \
--cc=jfeng@marvell.com \
--cc=kewei.mv@gmail.com \
--cc=kewei@marvell.com \
--cc=lil@marvell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=qswang@marvell.com \
--cc=qzhao@marvell.com \
--cc=saeed.bishara@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;
as well as URLs for NNTP newsgroup(s).