public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi@vger.kernel.org
Subject: Re: [SCSI] fix media change events for polled devices
Date: Fri, 21 Mar 2008 16:49:10 -0500	[thread overview]
Message-ID: <1206136150.2961.79.camel@localhost.localdomain> (raw)
In-Reply-To: <47E424E2.1030801@garzik.org>

On Fri, 2008-03-21 at 17:13 -0400, Jeff Garzik wrote:
> James Bottomley wrote:
> > On Fri, 2008-03-21 at 17:04 -0400, Jeff Garzik wrote:
> >> James Bottomley wrote:
> >>> It's fixed, and nothing else is additionally broken by the current fix.
> >> Other than the newly-inconsistent, exported-to-userspace interface, ITYM.
> > 
> > How is it newly inconsistent?  It can still be used in the manner you
> > intended it, namely to tell if the CD supports AN or not.  When we add
> > the new bit, we'll have to add a new file for it anyway.
> 
> Previously, the events could be expected to be sent (or sent) in strict 
> accordance with supported_events.

we don't publish supported_events; we publish a single file called
media_change.  Right at the moment its meaning is I have a 1 if AN is
supported and 0 if it's not.

Before the fix, its meaning was  1 if AN is supported and 0 if it's not.

The file name now looks wrong ... it should probably be an_media_change
or something if we have to introduce a new file called poll_media_chage
to distinguish them ... but nothing's changed about the way it works.

> Now, you are essentially sending out-of-band events, because the 
> receiver requested supported_events -- but is getting much more than that!
> 
> You broke a fundamental assumption of the interface -- that 
> supported_events accurately and fully represented all events sent via 
> the new API.

Anyway, realistically, since no CD or DVD on the market today seems to
support the AHCI AN method, this argument is really moot ... we just
need polling to work.

James



  reply	other threads:[~2008-03-21 21:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200803211559.m2LFxPi6017869@hera.kernel.org>
2008-03-21 17:12 ` [SCSI] fix media change events for polled devices Jeff Garzik
2008-03-21 17:31   ` Linus Torvalds
2008-03-21 19:38     ` James Bottomley
2008-03-21 20:54       ` Jeff Garzik
2008-03-21 20:39     ` Jeff Garzik
2008-03-21 18:33   ` Kay Sievers
2008-03-21 20:42     ` Jeff Garzik
2008-03-21 20:57       ` Kay Sievers
2008-03-21 21:04       ` James Bottomley
2008-03-21 21:10         ` Jeff Garzik
2008-03-21 19:44   ` James Bottomley
2008-03-21 20:36     ` Jeff Garzik
2008-03-21 21:01       ` James Bottomley
2008-03-21 21:04         ` Jeff Garzik
2008-03-21 21:09           ` James Bottomley
2008-03-21 21:13             ` Jeff Garzik
2008-03-21 21:49               ` James Bottomley [this message]
2008-03-21 22:35                 ` Jeff Garzik
2008-03-21 22:52                   ` James Bottomley
2008-03-25  3:09                     ` Jeff Garzik
2008-03-25  3:18                       ` James Bottomley

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=1206136150.2961.79.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=kay.sievers@vrfy.org \
    --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