From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Mark Haverkamp <markh@osdl.org>, linux-scsi <linux-scsi@vger.kernel.org>
Subject: RE: [PATCH] aacraid 2.6: Fix aacraid probe breakage inscsi-block-2.6.git
Date: Mon, 15 Aug 2005 12:20:09 -0500 [thread overview]
Message-ID: <1124126409.5089.30.camel@mulgrave> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F01708AE0@otce2k03.adaptec.com>
On Mon, 2005-08-15 at 13:06 -0400, Salyzyn, Mark wrote:
> The code does not 'damage' the scsi-misc tree version, so why not apply
> it to the scsi-misc tree as well at least to make sure it does not
> (extending the test coverage)? What is the scsi-block timetable for
> downstream?
OK, that's true ... there's no reason not to.
> I have almost religiously applied all patches that touch the driver to
> the Adaptec branch here. The net result is I have caught some gaffs
> early on because we always have some test or Q/A program ready to give
> it coverage.
Yes, early and often ... just in case the scsi-block merge gets delayed
again.
James
prev parent reply other threads:[~2005-08-15 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 17:06 [PATCH] aacraid 2.6: Fix aacraid probe breakage inscsi-block-2.6.git Salyzyn, Mark
2005-08-15 17:20 ` James Bottomley [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=1124126409.5089.30.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=markh@osdl.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