From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jeff Garzik <jgarzik@pobox.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 17:21:33 -0500 [thread overview]
Message-ID: <1111011693.6544.5.camel@mulgrave> (raw)
In-Reply-To: <42389797.7000004@pobox.com>
On Wed, 2005-03-16 at 15:31 -0500, Jeff Garzik wrote:
> More info? Were they dropped on purpose, or just never arrived?
> If dropped on purpose, what was the reason?
You posted substantive updates to a maintained driver. Adam Radford is
the maintainer, but I haven't heard anything from him (neither ACK, NAK
or "this is my latest set of updates containing these patches") so could
you poke him, please.
James
prev parent reply other threads:[~2005-03-16 22:22 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
2005-03-16 20:07 ` James Bottomley
2005-03-16 20:31 ` Jeff Garzik
2005-03-16 22:21 ` 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=1111011693.6544.5.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--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