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:22:32 -0500 [thread overview]
Message-ID: <1190478152.3347.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20070918015952.GA22742@lsil.com>
On Mon, 2007-09-17 at 19:59 -0600, Eric Moore wrote:
> 1) cleanup ioc_reset callback handlers, introducing wrappers for synronizing error recovery (mpt_set_taskmgmt_in_progress_flag, mpt_clear_taskmgmt_in_progress_flag), as the fusion firmware only handles one task management request at a time.
> 2) set vtarget->deleted flag when devices have been removed.
> 3) mdr@sgi.com - fix's provided from SGI after testing with single threaded internal commands
OK, I thought I'd wait here for the breakout, but in the meantime I
tried to compile the first five patches, but they don't:
CC [M] drivers/message/fusion/mptscsih.o
drivers/message/fusion/mptscsih.c: In function 'mptscsih_qcmd':
drivers/message/fusion/mptscsih.c:1357: error: 'MPT_SCSI_HOST' has no
member named 'resetPending'
drivers/message/fusion/mptscsih.c: In function 'mptscsih_TMHandler':
drivers/message/fusion/mptscsih.c:1554: error: 'MPT_ADAPTER' has no
member named 'diagLock'
...
The series can't be applied in this form, because if git bisect steps
into the middle of this, the compile will break (and hence the
bisection) and a lot of people will say a lot of nasty things.
A patch series really needs to be one patch per logical change (with
other peoples' patches broken out) in a form that is separately
compilable for each patch. Additionally, with a separate change log and
summary (i.e. not four patches all saying "mpt fusion: error recovery
improvements, and synchronizing internal commands").
I'll back all of this out; can you resend the series conforming to the
above request?
Thanks,
James
next prev parent reply other threads:[~2007-09-22 16:22 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
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 ` James Bottomley [this message]
2007-09-25 1:26 ` 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=1190478152.3347.25.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox