From: Arjan van de Ven <arjan@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>
Subject: Re: [PATCHv2 0/4] scsi: export and clean up headers
Date: Tue, 29 Sep 2009 12:46:20 +0200 [thread overview]
Message-ID: <20090929124620.2c8abc4d@infradead.org> (raw)
In-Reply-To: <20090929103353.GA11183@redhat.com>
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)
If not, do you know what it would take to get to that point?
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-09-29 10:45 UTC|newest]
Thread overview: 8+ 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 [this message]
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
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=20090929124620.2c8abc4d@infradead.org \
--to=arjan@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox