mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Grant Grundler <iod00d@hp.com>
Cc: Roland Dreier <rolandd@cisco.com>,
	linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [openib-general] Re: [RFC] Move InfiniBand .h files
Date: Thu, 04 Aug 2005 21:51:10 +0200	[thread overview]
Message-ID: <1123185070.3318.49.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050804182652.GF20422@esmail.cup.hp.com>

On Thu, 2005-08-04 at 11:26 -0700, Grant Grundler wrote:
> On Thu, Aug 04, 2005 at 07:53:58PM +0200, Arjan van de Ven wrote:
> > On Thu, 2005-08-04 at 10:32 -0700, Roland Dreier wrote:
> > > I would like to get people's reactions to moving the InfiniBand .h
> > > files from their current location in drivers/infiniband/include/ to
> > > include/linux/rdma/.  If we agree that this is a good idea then I'll
> > > push this change as soon as 2.6.14 starts.
> > 
> > please only put userspace clean headers here; the rest is more or less
> > private headers for your subsystem. 
> 
> Sorry...this smells like a rathole...but does this mean
> linus agrees the kernel subsystems should export headers suitable for
> both user space and kernel driver modules?
> 
> Historical, I thought glibc and other user space libs were expected to
> maintain their own set of header files. Maybe I'm just confused...

there is a definite requirement for the kernel to expose SOME things to
userspace. Well for SOMETHING to expose them. Right now most distros
ship a hacked up version of the kernel headers (eg removed of all the
kernel specific stuff and all the gpl inline code etc). A good part of
making such an external project possible is to make a clean separation
between userspace shared stuff and pure kernel internals.



  reply	other threads:[~2005-08-04 19:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 17:32 Roland Dreier
2005-08-04 17:48 ` [openib-general] " Tom Duffy
2005-08-04 17:53 ` Arjan van de Ven
2005-08-04 18:26   ` [openib-general] " Grant Grundler
2005-08-04 19:51     ` Arjan van de Ven [this message]
2005-08-04 18:31   ` Roland Dreier
2005-08-04 18:38     ` Arjan van de Ven
2005-08-04 18:57       ` Roland Dreier
2005-08-04 19:22         ` Sam Ravnborg
2005-08-04 19:54           ` Christopher Friesen
2005-08-04 20:02             ` Sam Ravnborg
2005-08-04 19:51         ` Arjan van de Ven
2005-08-04 18:11 ` [openib-general] " Steve Wise
2005-08-04 18:20 ` Grant Grundler
2005-08-04 18:32   ` Roland Dreier
2005-08-04 21:38 ` James Lentini
2005-08-05  9:22 ` Christoph Hellwig
2005-08-05 16:08   ` Roland Dreier
2005-08-05 21:06     ` Sam Ravnborg

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=1123185070.3318.49.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=iod00d@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rolandd@cisco.com \
    /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

all inboxes | Powered by JetHome®