From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH] SCSI updates for 2.6.11
Date: Wed, 16 Mar 2005 13:35:40 -0500 [thread overview]
Message-ID: <42387C7C.9040407@pobox.com> (raw)
In-Reply-To: <1110934411.5685.39.camel@mulgrave>
James Bottomley wrote:
> This is my current tranch of patches that were waiting the transition
> from -rc to released (sorry it's late ... I've been on holiday).
>
> The patch is available here:
>
> bk://linux-scsi.bkbits.net/scsi-for-linus-2.6
Are my 3ware bugfixes in the queue? Currently 3ware claims it handled
the interrupt, even the interrupt is a shared one and the event was
meant for another driver.
Jeff
next prev parent reply other threads:[~2005-03-16 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 0:53 [BK PATCH] SCSI updates for 2.6.11 James Bottomley
2005-03-16 18:35 ` Jeff Garzik [this message]
2005-03-16 20:07 ` James Bottomley
2005-03-16 20:31 ` Jeff Garzik
2005-03-16 22:21 ` 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=42387C7C.9040407@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@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