mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Steve Wise" <swise@ammasso.com>
To: "'Roland Dreier'" <rolandd@cisco.com>,
	<openib-general@openib.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [openib-general] [RFC] Move InfiniBand .h files
Date: Thu, 4 Aug 2005 13:11:10 -0500	[thread overview]
Message-ID: <MAIL2XR08ies8JynCR3000005b2@mail2.ammasso.com> (raw)
In-Reply-To: <52iryla9r5.fsf@cisco.com>

Seems reasonable to me...


Steve.

 

> -----Original Message-----
> From: openib-general-bounces@openib.org 
> [mailto:openib-general-bounces@openib.org] On Behalf Of Roland Dreier
> Sent: Thursday, August 04, 2005 12:32 PM
> To: openib-general@openib.org; linux-kernel@vger.kernel.org
> Subject: [openib-general] [RFC] Move InfiniBand .h files
> 
> 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.
> 
> The advantages of doing this are:
> 
>   - The headers become more easily accessible to other parts of the
>     tree that might want to use IB support.  For example, an NFS/RDMA
>     client probably wants to live under fs/
>   - It makes it easier to build IB modules outside the tree, since
>     include/linux gets put in /lib/modules/<ver>/build.  I realize
>     that we don't really care about out-of-tree modules, but it is
>     convenient to be able to develop and distribute new drivers that
>     build against someone's existing kernels.
>   - We can kill off the ugly
> 
>         EXTRA_CFLAGS += -Idrivers/infiniband/include
> 
>     lines in our Makefiles.
> 
> The disadvantages are:
> 
>   - It's churn with little technical merit.
>   - It makes it a little harder to pull the OpenIB svn tree into a
>     kernel tree, since one would have to link both drivers/infiniband
>     and include/linux/rdma instead of just drivers/infiniband.  This
>     problem goes away if/when OpenIB shifts over to a new source code
>     control system.
> 
> Thanks,
>   Roland
> _______________________________________________
> openib-general mailing list
> openib-general@openib.org
> http://openib.org/mailman/listinfo/openib-general
> 
> To unsubscribe, please visit 
> http://openib.org/mailman/listinfo/openib-general
> 


  parent reply	other threads:[~2005-08-04 18:11 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
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 ` Steve Wise [this message]
2005-08-04 18:20 ` [openib-general] " 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=MAIL2XR08ies8JynCR3000005b2@mail2.ammasso.com \
    --to=swise@ammasso.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®