All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Boaz Harrosh <bharrosh@panasas.com>,
	Ulrich Drepper <drepper@redhat.com>
Subject: Re: [PATCHv2 0/4] scsi: export and clean up headers
Date: Sun, 4 Oct 2009 13:16:26 +0200	[thread overview]
Message-ID: <20091004111626.GA17057@redhat.com> (raw)
In-Reply-To: <20090930071555.GA13915@merkur.ravnborg.org>

On Wed, Sep 30, 2009 at 09:15:55AM +0200, Sam Ravnborg wrote:
> 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/ .  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).
> 
> The scsi headers are exported. So it does not matter if glibc or any
> other libc for that amtter uses the headers or not.
> Exported headers has some rules to follow and scsi are no exception here.
> 
> Now if we get the scsi headers in good shape then and only then we can 
> go to glibc people and tell them that we have a better set of scsi headers
> than they have.
> 
> Postponing updates to the exported scsi headers just beacause we do not
> have any users of them at the moment is the wrong thing to do.
> We should rather use the opportunity to streamline the exported headers
> so we have a superior set of headers to offer.
> 
> 	Sam

Ulrich, does it create problems for you if we fix kernel headers for scsi?
Does it make your life easier?

-- 
MST

  reply	other threads:[~2009-10-04 11:19 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
2009-09-29 12:56   ` Michael S. Tsirkin
2009-09-30  7:15   ` Sam Ravnborg
2009-10-04 11:16     ` Michael S. Tsirkin [this message]
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=20091004111626.GA17057@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 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.