From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: linux-ide@vger.kernel.org, kristen.c.accardi@intel.com,
James.Bottomley@steeleye.com, htejun@gmail.com
Subject: Re: [patch 06/10] scsi: expose AN support to user space
Date: Wed, 03 Oct 2007 16:39:00 -0400 [thread overview]
Message-ID: <4703FDE4.5060301@garzik.org> (raw)
In-Reply-To: <200710022053.l92Kr2ka021694@imap1.linux-foundation.org>
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>
> Cc: 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>
ACK
Though I either (a) would like SCSI maintainers to apply this, or (b)
would like SCSI maintainers to ACK this before I apply it myself.
Or IOW, if others are happy, I'm happy :)
The follow-up patch "libata: expose AN to user space" requires this one
in order to compile, so it has the same fate.
Additional background, for those interested: libata-dev.git#upstream
(2.6.24 queue) already contains Kristen's libata-specific portions of
the media event notification. Internally, all the "guts" are there, and
we currently call a no-op function that's waiting for the SCSI guts:
void ata_scsi_media_change_notify(struct ata_device *dev)
{
#ifdef OTHER_AN_PATCHES_HAVE_BEEN_APPLIED
if (dev->sdev)
scsi_device_event_notify(dev->sdev, SDEV_MEDIA_CHANGE);
#endif
}
Regards,
Jeff
prev parent reply other threads:[~2007-10-03 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 20:53 [patch 06/10] scsi: expose AN support to user space akpm
2007-10-03 20:39 ` Jeff Garzik [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=4703FDE4.5060301@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-ide@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;
as well as URLs for NNTP newsgroup(s).