From: Christoph Hellwig <hch@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
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 08:43:47 -0400 [thread overview]
Message-ID: <20090929124347.GA11375@infradead.org> (raw)
In-Reply-To: <20090929103353.GA11183@redhat.com>
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/ . 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).
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.
next prev parent reply other threads:[~2009-09-29 12:43 UTC|newest]
Thread overview: 9+ 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 [this message]
2009-09-29 12:56 ` Michael S. Tsirkin
2009-09-30 7:15 ` Sam Ravnborg
2009-10-04 11:16 ` Michael S. Tsirkin
2009-12-21 14:14 ` Mike Frysinger
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=20090929124347.GA11375@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--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 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.