From: James Bottomley <James.Bottomley@suse.de>
To: "Kashyap, Desai" <kashyap.desai@lsi.com>
Cc: linux-scsi@vger.kernel.org, Eric.Moore@lsi.com, Sathya.Prakash@lsi.com
Subject: Re: [PATCH 1/7] mpt2sas : Rescan topology from Interrupt context instead of work queue
Date: Fri, 14 Aug 2009 14:59:40 +0000 [thread overview]
Message-ID: <1250261980.4021.7.camel@mulgrave.site> (raw)
In-Reply-To: <20090814094253.GC29415@lsi.com>
On Fri, 2009-08-14 at 15:13 +0530, Kashyap, Desai wrote:
> Following host reset its possible that the controller firmware could
> assign new handles for devices, as well as adding or deleting devices. There is
> code in the driver that will rescan the topology folowing host reset; updating
> device handles, and remove devices that are no longer responding. This patch
> will improve the responsivness by moving this rescaning from the delayed hotplug
> worker thread to immediately following the host reset.
>
> ---
>
> Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
> Signed-off-by: Eric Moore <Eric.moore@lsi.com>
For the third time of asking, can you put the signoffs *before* the
three dashes that tell the git importer to ignore the rest of the text
before the patch?
Also, what exactly do these signoffs mean ... they're supposed to track
author and whose hands these patches have been through. If Eric wrote
them, and you're just submitting them, I need a From: field at the
beginning to change the git authorship (and also the order of signoff
needs reversing).
James
next parent reply other threads:[~2009-08-14 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090814094253.GC29415@lsi.com>
2009-08-14 14:59 ` James Bottomley [this message]
2009-08-14 15:05 ` [PATCH 1/7] mpt2sas : Rescan topology from Interrupt context instead of work queue Moore, Eric
2009-08-14 15:13 ` James Bottomley
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=1250261980.4021.7.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=Eric.Moore@lsi.com \
--cc=Sathya.Prakash@lsi.com \
--cc=kashyap.desai@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