Date: Tue, 29 Sep 2009 13:19:20 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
       linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
       Boaz Harrosh <bharrosh@panasas.com>, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCHv2 0/4] scsi: export and clean up headers
Message-ID: <20090929111918.GA17799@redhat.com>
References: <20090929103353.GA11183@redhat.com> <20090929124620.2c8abc4d@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090929124620.2c8abc4d@infradead.org>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1390
Lines: 35

On Tue, Sep 29, 2009 at 12:46:20PM +0200, Arjan van de Ven wrote:
> On Tue, 29 Sep 2009 12:33:53 +0200
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > This implements a minor cleanup of exported scsi headers,
> > and adds export of headers that are de-facto used by userspace.
> > The patches are on top of 2.6.32-rc1.
> > Can these be queued for 2.6.32?
> > Thanks.
> > 
> 
> one of the problems I've found is that glibc has its own copy
> of scsi headers, causing interesting conflicts. Do you know for
> sure that with these cleanups we can retire the glibc headers?
> (that would be very welcome)

I don't see why not.
The only differences with glibc headers that I can see:
- glic adds #include <features.h> on top of each header
- glibc has old SCSI_IOCTL_TAGGED_ENABLE/SCSI_IOCTL_TAGGED_DISABLE

> If not, do you know what it would take to get to that point?

Probably just talk to Ulrich or other glibc developers.
If there's some symbol that's missing, we can always add it.

> -- 
> Arjan van de Ven 	Intel Open Source Technology Centre
> For development, discussion and tips for power savings, 
> visit http://www.lesswatts.org
--
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/