From: Jeff Garzik <jeff@garzik.org>
To: James.Bottomley@steeleye.com, linux-scsi <linux-scsi@vger.kernel.org>
Cc: akpm@linux-foundation.org, kristen.c.accardi@intel.com,
htejun@gmail.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch 1/1] scsi: expose AN support to user space
Date: Mon, 15 Oct 2007 14:12:15 -0400 [thread overview]
Message-ID: <4713AD7F.8030906@garzik.org> (raw)
In-Reply-To: <470FE29A.7050605@garzik.org>
Jeff Garzik wrote:
> akpm@linux-foundation.org wrote:
>> From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
>>
>> If a scsi_device supports async notification for media change, then
>> let user
>> space know this capability exists by creating a new sysfs entry
>> "media_change_notify", which will be 1 if it is supported, and 0 if not
>> supported. Create a routine which allows scsi devices to send a
>> uevent when
>> media change events occur.
>>
>> Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
>> Acked-by: Jeff Garzik <jeff@garzik.org>
>> Cc: Tejun Heo <htejun@gmail.com>
>> Cc: James Bottomley <James.Bottomley@steeleye.com>
>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>
> Ping?
Re-Ping?
This patch works (it has been working for months), is ACK'd by me,
addresses some of the feedback given in August, and has not received any
comments despite the SCSI maintainers being To'd or CC'd for weeks
(months, if you include the older thread).
Further, this patch is required to round out interrupt-driven media
change notification, that which eliminates the CD-ROM polling that
userspace has done since the dawn of time.
It was not in the merge window SCSI push, while being in -mm for a while
and linux-scsi having the patch for a while. Which means, if the
silence continues, it must wait 4-6 months for 2.6.25 release, for no
apparent reason.
Jeff
parent reply other threads:[~2007-10-15 18:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <470FE29A.7050605@garzik.org>]
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=4713AD7F.8030906@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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