Date: Wed, 15 Aug 2007 09:27:31 -0700
From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org,
       linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
       akpm@linux-foundation.org
Subject: Re: [patch 2/4] scsi: expose AN support to user space
Message-Id: <20070815092731.01b19e0e.kristen.c.accardi@intel.com>
In-Reply-To: <1187186509.3327.7.camel@localhost.localdomain>
References: <20070808190613.616085010@localhost.localdomain>
	<20070808120822.9cf187bb.kristen.c.accardi@intel.com>
	<46C2B59A.6070200@garzik.org>
	<1187186509.3327.7.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1593
Lines: 36

On Wed, 15 Aug 2007 09:01:49 -0500
James Bottomley <James.Bottomley@SteelEye.com> wrote:

> On Wed, 2007-08-15 at 04:13 -0400, Jeff Garzik wrote:
> > Kristen Carlson Accardi wrote:
> > > 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>
> > 
> > if James is happy with this patch, I'm happy with patch #2 and #3
> 
> Actually, we just got a second potential consumer ... although I'll
> reprod to have the reporter send it to the list.  It's a device that
> needs notice of report luns data changing.  The proposed mechanism looks
> a bit narrow now (too tied to media change).  I'll see if I can propose
> a more generic update.
> 
> James
> 

Too narrow because it's tied to scsi_device?  Obviously it'd be easy
to expand the scsi_device_event enum to include LUNS_DATA_CHANGE or 
something, and even the scsi_device_event_info struct can easily be 
expanded if you need more info attached to the event.  Let me know if 
there's something specific I can help with.

Kristen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/