From: Greg KH <greg@kroah.com>
To: Roland Dreier <roland@topspin.com>
Cc: linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH][RFC/v1][0/12] Initial submission of InfiniBand patches for review
Date: Mon, 22 Nov 2004 14:13:04 -0800 [thread overview]
Message-ID: <20041122221304.GA15634@kroah.com> (raw)
In-Reply-To: <20041122713.Nh0zRPbm8qA0VBxj@topspin.com>
On Mon, Nov 22, 2004 at 07:13:24AM -0800, Roland Dreier wrote:
> organization of the code will be very much appreciated. For example,
> the current set of patches puts include files in driver/infiniband/include;
> would it be preferred to put include files in include/linux/infiniband/,
> directly in include/linux, or perhaps in include/infiniband?
Who would be including these files, only drivers in drivers/infiniband?
Or from files in other parts of the kernel?
If from other parts of the kernel, use include/linux/infiniband.
thanks,
greg k-h
next prev parent reply other threads:[~2004-11-22 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:13 [PATCH][RFC/v1][0/12] Initial submission of InfiniBand patches for review Roland Dreier
2004-11-22 22:13 ` Greg KH [this message]
2004-11-22 22:50 ` Roland Dreier
2004-11-22 23:01 ` Greg KH
2004-11-23 12:13 ` Arnd Bergmann
2004-11-23 15:20 ` Roland Dreier
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=20041122221304.GA15634@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=roland@topspin.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