From: James Bottomley <James.Bottomley@SteelEye.com>
To: Eric Moore <eric.moore@lsi.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 6/9] mpt fusion: error recovery improvements, and synchronizing internal commands
Date: Sat, 22 Sep 2007 11:01:51 -0500 [thread overview]
Message-ID: <1190476911.3347.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20070918015952.GA22742@lsil.com>
On Mon, 2007-09-17 at 19:59 -0600, Eric Moore wrote:
> 3) mdr@sgi.com - fix's provided from SGI after testing with single threaded internal commands
What fixes?
The object of a change log is to preserve the history of a particular
change (as per the Developer Certificate of Origin). This means if you
get a patch from someone, you should also collect their signoff with it,
then you pass it on to me complete with your signoff added (and a note
if you had to modify it to fit it into the patch series or otherwise
alter it).
James
next prev parent reply other threads:[~2007-09-22 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 1:59 [PATCH 6/9] mpt fusion: error recovery improvements, and synchronizing internal commands Eric Moore
2007-09-22 16:01 ` James Bottomley [this message]
2007-09-25 1:35 ` [PATCH 6/9] mpt fusion: error recovery improvements, andsynchronizing " Moore, Eric
2007-09-25 17:35 ` James Bottomley
2007-09-22 16:22 ` [PATCH 6/9] mpt fusion: error recovery improvements, and synchronizing " James Bottomley
2007-09-25 1:26 ` [PATCH 6/9] mpt fusion: error recovery improvements, andsynchronizing " Moore, Eric
2007-09-25 17:32 ` James Bottomley
2007-09-25 18:22 ` [PATCH 6/9] mpt fusion: error recovery improvements,andsynchronizing " Moore, Eric
2007-09-25 18:37 ` Jeff Garzik
2007-09-25 22:38 ` Michael Reed
2007-09-25 22:57 ` James Bottomley
2007-09-25 23:31 ` Jeff Garzik
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=1190476911.3347.19.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=eric.moore@lsi.com \
--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 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.