From: Roland Dreier <rdreier@cisco.com>
To: "Bryan O'Sullivan" <bos@pathscale.com>, sam@ravnborg.org
Cc: linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH 16 of 16] ipath - kbuild infrastructure
Date: Thu, 30 Mar 2006 14:36:34 -0800 [thread overview]
Message-ID: <ada64lv1rwt.fsf@cisco.com> (raw)
In-Reply-To: <1143755751.24402.11.camel@chalcedony.internal.keyresearch.com> (Bryan O'Sullivan's message of "Thu, 30 Mar 2006 13:55:51 -0800")
Bryan> I did ask at one point whether the core driver should live
Bryan> in a directory in drivers/char/, since it's not really an
Bryan> IB driver at all, and just have the IB-specific stuff live
Bryan> in drivers/infiniband/hw/.
I guess we could do that (now or later).
For now how about something minimal like the change below?
Sam, does this seem OK to you? (The situation is that the IPATH_CORE
source physically sits in drivers/infiniband/hw/ipath, but it is
possible to enable IPATH_CORE without enabling INFINIBAND. So we need
to tell the build system to descend into drivers/infiniband if
IPATH_CORE is enabled, even if INFINIBAND isn't enabled)
Thanks,
Roland
diff --git a/drivers/Makefile b/drivers/Makefile
index 4249552..2449ec5 100644
--- a/drivers/Makefile
+++ b/drivers/Makefile
@@ -70,6 +70,7 @@ obj-$(CONFIG_EISA) += eisa/
obj-$(CONFIG_CPU_FREQ) += cpufreq/
obj-$(CONFIG_MMC) += mmc/
obj-$(CONFIG_INFINIBAND) += infiniband/
+obj-$(CONFIG_IPATH_CORE) += infiniband/
obj-$(CONFIG_SGI_SN) += sn/
obj-y += firmware/
obj-$(CONFIG_CRYPTO) += crypto/
next prev parent reply other threads:[~2006-03-30 22:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 23:23 [PATCH 0 of 16] ipath - driver submission for 2.6.17 Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 1 of 16] ipath - core device driver Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 2 of 16] ipath - core driver header files Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 3 of 16] ipath - support for HyperTransport devices Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 4 of 16] ipath - support for PCI Express devices Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 5 of 16] ipath - chip initialisation code, and diag support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 6 of 16] ipath - misc driver support code Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 7 of 16] ipath - sysfs and ipathfs support for core driver Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 8 of 16] ipath - support for userspace apps using " Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 9 of 16] ipath - layering interfaces used by higher-level driver code Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 10 of 16] ipath - infiniband header files Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 11 of 16] ipath - infiniband UC and UD protocol support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 12 of 16] ipath - infiniband RC " Bryan O'Sullivan
2006-03-30 20:36 ` Pavel Machek
2006-03-29 23:23 ` [PATCH 13 of 16] ipath - misc infiniband code, part 1 Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 14 of 16] ipath - misc infiniband code, part 2 Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 15 of 16] ipath - infiniband verbs support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 16 of 16] ipath - kbuild infrastructure Bryan O'Sullivan
2006-03-30 21:06 ` Roland Dreier
2006-03-30 21:55 ` Bryan O'Sullivan
2006-03-30 22:36 ` Roland Dreier [this message]
2006-03-31 3:53 ` Sam Ravnborg
2006-03-30 20:59 ` [PATCH 0 of 16] ipath - driver submission for 2.6.17 Roland Dreier
2006-03-30 21:54 ` Bryan O'Sullivan
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=ada64lv1rwt.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=bos@pathscale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--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