From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-ide@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [patch 2/3] libata: expose AN support to user space via sysfs
Date: Thu, 05 Apr 2007 04:03:20 -0400 [thread overview]
Message-ID: <4614AD48.1080005@pobox.com> (raw)
In-Reply-To: <460B26AB.8060307@gmail.com>
Tejun Heo wrote:
> Jeff Garzik wrote:
>> AN is a generic concept that I feel will propagate elsewhere.
>
> I think SCSI already has it or am I imagining things again? :-)
>
>> Though perhaps it should be in a 'capability_flags' file rather than a
>> 'media_change_event' file.
>
> IMHO, if it's genhd.capability_flags then the flag should be
> MEDIA_CHANGE_NOTIFY not ASYNC_NOTIFICATION because AN itself doesn't
> imply any specific event. It's just a notification mechanism, for ATAPI
> devices, it means media change, for PMP it has a different meaning, so I
> think we need to export the processed meaning not the specific mechanism
> to userland.
Agreed, sounds good.
Jeff
next prev parent reply other threads:[~2007-04-05 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070328230108.597741522@intel.com>
2007-03-28 23:44 ` [patch 1/3] libata: check for AN support Kristen Carlson Accardi
2007-03-29 1:53 ` Tejun Heo
2007-03-29 2:02 ` Jeff Garzik
2007-03-28 23:44 ` [patch 2/3] libata: expose AN support to user space via sysfs Kristen Carlson Accardi
2007-03-29 0:15 ` Jeff Garzik
2007-03-29 2:07 ` Tejun Heo
2007-03-29 2:19 ` Jeff Garzik
2007-03-29 2:38 ` Tejun Heo
2007-04-05 8:03 ` Jeff Garzik [this message]
2007-03-29 2:04 ` Tejun Heo
2007-03-28 23:44 ` [patch 3/3] libata: handle AN interrupt Kristen Carlson Accardi
2007-03-29 2:13 ` Tejun Heo
[not found] <20070321004740.939006166@intel.com>
2007-03-21 0:52 ` [patch 2/3] libata: expose AN support to user space via sysfs Kristen Carlson Accardi
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=4614AD48.1080005@pobox.com \
--to=jgarzik@pobox.com \
--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.