From: Jeff Garzik <jeff@garzik.org>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, htejun@gmail.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 0/7] Asynchronous Notification for ATAPI devices (resend)
Date: Thu, 24 May 2007 23:14:13 -0400 [thread overview]
Message-ID: <46565485.3000602@garzik.org> (raw)
In-Reply-To: <20070509163756.dd8136c7.kristen.c.accardi@intel.com>
Kristen Carlson Accardi wrote:
> Hi Jeff,
> Here are the AN patches again, they have not changed with the exception
> of patch #1, which does set the host flag in board_ahci and board_ahci_pi
> now (thanks Tejun).
>
> This patch series implements Asynchronous Notification (AN) for SATA
> ATAPI devices as defined in SATA 2.5 and AHCI 1.1 and higher. Drives
> which support this feature will send a notification when new media is
> inserted and removed, preventing the need for user space to poll for
> new media. This support is exposed to user space via a flag that will
> be set in /sys/block/sr*/capability_flags. If the flag is set, user
> space can disable polling for the new media, and the genhd driver will
> send a KOBJ_CHANGE event with the envp set to MEDIA_CHANGE_EVENT=1.
>
> Note that this patch only implements support for directly attached
> drives - AN with drives attached to a port multiplier requires
> additional changes.
Patches look OK to me... it will take some coordination for the
non-libata bits. I think Andrew mentioned some of this. And if the
SCSI bits get stuck in the SCSI maintainer's bit bucket, let me know.
Jeff
prev parent reply other threads:[~2007-05-25 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 23:37 [patch 0/7] Asynchronous Notification for ATAPI devices (resend) Kristen Carlson Accardi
2007-05-25 3:14 ` 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=46565485.3000602@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.