From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christoph Hellwig <hch@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>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: [PATCHv2 0/4] scsi: export and clean up headers
Date: Tue, 29 Sep 2009 14:56:59 +0200 [thread overview]
Message-ID: <20090929125657.GA26932@redhat.com> (raw)
In-Reply-To: <20090929124347.GA11375@infradead.org>
On Tue, Sep 29, 2009 at 08:43:47AM -0400, Christoph Hellwig wrote:
> On Tue, Sep 29, 2009 at 12:33:53PM +0200, Michael S. Tsirkin 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.
>
> Before we do anything in this area we need to find an agreement who
> owns /usr/include/scsi/ .
Let's cleanup headers that we already export (that's patches 1/2 in the
series). I don't see a reason to delay that, do you?
> Right now that's glibc, and if we want to
> change it to the kernel headers we need to find a transition agreement
> with the glibc maintainer (aka mostly Uli).
Who cares? If glibc wants to carry its own headers, let it. It will
likely switch if what kernel provides is sane (it is currently not). So
let's start with cleaning up what we already have. If glibc decides not
to use it, no harm's done.
> And even then it's quite questionable if the kernel should provide
> scsi.h as it's mostly protocol defintions, not actually a kernel
> interface.
It has a ton of ioctl definitions there.
--
MST
next prev parent reply other threads:[~2009-09-29 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 10:33 [PATCHv2 0/4] scsi: export and clean up headers Michael S. Tsirkin
2009-09-29 10:46 ` Arjan van de Ven
2009-09-29 11:19 ` Michael S. Tsirkin
2009-09-29 12:43 ` Christoph Hellwig
2009-09-29 12:56 ` Michael S. Tsirkin [this message]
2009-09-30 7:15 ` Sam Ravnborg
2009-12-21 14:14 ` Mike Frysinger
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=20090929125657.GA26932@redhat.com \
--to=mst@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.com \
--cc=drepper@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).