From: Roland Dreier <roland@topspin.com>
To: linux-kernel@vger.kernel.org
Cc: openib-general@openib.org
Subject: Re: [PATCH][RFC/v2][1/21] Add core InfiniBand support (public headers)
Date: Wed, 24 Nov 2004 11:39:27 -0800 [thread overview]
Message-ID: <52brdnyr2o.fsf@topspin.com> (raw)
In-Reply-To: <20041123195345.GC8367@mars.ravnborg.org> (Sam Ravnborg's message of "Tue, 23 Nov 2004 20:53:45 +0100")
Sam> After giving it a second thought my vote goes for:
Sam> include/linux/infiniband
Could you share the reasoning that led to that preference?
Unfortunately we don't seem to be converging on one choice of location.
On one side there is the fact that the .h files are not used outside
of drivers/infiniband -- hence they should stay under drivers/infiniband.
On the other side is the fact that moving the includes under include/
gets rid of some CFLAGS lines in the Makefile.
I don't see a conclusive reason to choose any particular place.
Perhaps Linus or Andrew can simply hand down an authoritative answer?
Thanks,
Roland
prev parent reply other threads:[~2004-11-25 2:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 16:14 [PATCH][RFC/v2][0/21] Second submission of InfiniBand patches for review Roland Dreier
2004-11-23 16:14 ` [PATCH][RFC/v2][1/21] Add core InfiniBand support (public headers) Roland Dreier
2004-11-23 16:14 ` [PATCH][RFC/v2][2/21] Add core InfiniBand support Roland Dreier
2004-11-23 16:14 ` [PATCH][RFC/v2][3/21] Hook up drivers/infiniband Roland Dreier
2004-11-23 16:14 ` [PATCH][RFC/v2][4/21] Add InfiniBand MAD (management datagram) support (public headers) Roland Dreier
2004-11-23 16:14 ` [PATCH][RFC/v2][5/21] Add InfiniBand MAD (management datagram) support Roland Dreier
2004-11-23 16:14 ` [PATCH][RFC/v2][6/21] Add InfiniBand SA (Subnet Administration) query support Roland Dreier
2004-11-23 16:14 ` [PATCH][RFC/v2][7/21] Add Mellanox HCA low-level driver Roland Dreier
2004-11-23 16:14 ` [PATCH][RFC/v2][8/21] Add Mellanox HCA low-level driver (midlayer interface) Roland Dreier
2004-11-23 16:15 ` [PATCH][RFC/v2][9/21] Add Mellanox HCA low-level driver (FW commands) Roland Dreier
2004-11-23 16:15 ` [PATCH][RFC/v2][10/21] Add Mellanox HCA low-level driver (EQ) Roland Dreier
2004-11-23 16:15 ` [PATCH][RFC/v2][11/21] Add Mellanox HCA low-level driver (initialization) Roland Dreier
2004-11-23 16:15 ` [PATCH][RFC/v2][12/21] Add Mellanox HCA low-level driver (QP/CQ) Roland Dreier
2004-11-23 16:15 ` [PATCH][RFC/v2][13/21] Add Mellanox HCA low-level driver (last bits) Roland Dreier
2004-11-23 16:15 ` [PATCH][RFC/v2][14/21] Add Mellanox HCA low-level driver (MAD) Roland Dreier
2004-11-23 16:15 ` [PATCH][RFC/v2][15/21] IPoIB IPv4 multicast Roland Dreier
2004-11-23 16:15 ` [PATCH][RFC/v2][16/21] IPoIB IPv6 support Roland Dreier
2004-11-23 16:16 ` [PATCH][RFC/v2][17/21] Add IPoIB (IP-over-InfiniBand) driver Roland Dreier
2004-11-23 16:16 ` [PATCH][RFC/v2][18/21] Add InfiniBand userspace MAD support Roland Dreier
2004-11-23 16:16 ` [PATCH][RFC/v2][19/21] Document InfiniBand ioctl use Roland Dreier
2004-11-23 16:16 ` [PATCH][RFC/v2][20/21] Add InfiniBand Documentation files Roland Dreier
2004-11-23 16:16 ` [PATCH][RFC/v2][21/21] InfiniBand MAINTAINERS entry Roland Dreier
2004-11-23 19:56 ` [PATCH][RFC/v2][4/21] Add InfiniBand MAD (management datagram) support (public headers) Sam Ravnborg
2004-11-23 17:22 ` [PATCH][RFC/v2][2/21] Add core InfiniBand support Greg KH
2004-11-23 17:34 ` Roland Dreier
2004-11-23 23:31 ` Roland Dreier
2004-11-24 0:13 ` Adrian Bunk
2004-11-24 0:24 ` Roland Dreier
2004-11-23 19:53 ` [PATCH][RFC/v2][1/21] Add core InfiniBand support (public headers) Sam Ravnborg
2004-11-24 19:39 ` Roland Dreier [this message]
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=52brdnyr2o.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.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