From: Roland Dreier <rdreier@cisco.com>
To: <glenng@NetEffect.com>
Cc: <openib-general@openib.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/9] NetEffect 10Gb RNIC Driver: kernel Kconfig and makefiles
Date: Thu, 26 Oct 2006 16:58:41 -0700 [thread overview]
Message-ID: <adawt6m634e.fsf@cisco.com> (raw)
In-Reply-To: <5E701717F2B2ED4EA60F87C8AA57B7CC064C9EAF@venom2> (Glenn Grundstrom's message of "Thu, 26 Oct 2006 18:45:39 -0500")
> +source "drivers/infiniband/hw/nes/Kconfig"
> +
> source "drivers/infiniband/hw/cxgb3/Kconfig"
This patch seems to be against some non-standard tree, since cxgb3
isn't upstream yet. And if cxgb3 were already upstream, it might be
polite to add yourself after it rather than before ;)
> +config INFINIBAND_NES_DEBUG
> + bool "Verbose debugging output"
> + depends on INFINIBAND_NES
> + default n
> + ---help---
> + This option causes the NetEffect RNIC driver to produce debug
> + messages. Select this if you are developing the driver
> + or trying to diagnose a problem.
I recommend making this option invisible unless EMBEDDED is set, and
having the default be 'y', and making your debugging level changeable
at run-time. That way everyone (in particular distros) will have this
turned on and you'll be able to figure out problems without making
end-users rebuild a kernel.
> +EXTRA_CFLAGS += -Idrivers/infiniband/include
Not needed in the kernel tree.
> -Idrivers/infiniband/hw/nes/nes_tcpip/include
I guess this is the mysterious TCP stack module. Anyway if you need
this in the end, I would suggest removing the C flag and using
#include "nes_tcpip/blah.h" in your source.
> +ifdef CONFIG_INFINIBAND_NES_DEBUG
> +EXTRA_CFLAGS += -DNES_DEBUG
> +endif
There's no point to this -- just test CONFIG_INFINIBAND_NES_DEBUG directly.
> +ifneq ($(KERNELRELEASE),)
> + obj-$(CONFIG_INFINIBAND_NES) += iw_nes.o
> +
> + iw_nes-objs := \
> + nes.o \
> + nes_hw.o \
> + nes_nic.o \
> + nes_cm.o \
> + nes_utils.o \
> + nes_verbs.o
> +else
This should be your whole Makefile -- we're not going to merge stuff
into the kernel tree to build your module out of the kernel tree.
Also it's more idiomatic to put all your component objects onto one
(or a few) lines.
- R.
next prev parent reply other threads:[~2006-10-26 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 23:45 [PATCH 1/9] NetEffect 10Gb RNIC Driver: kernel Kconfig and makefiles Glenn Grundstrom
2006-10-26 23:58 ` Roland Dreier [this message]
2006-10-27 0:04 ` David Miller
2006-10-27 0:21 ` Roland Dreier
2006-10-27 14:39 ` [openib-general] " James Lentini
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=adawt6m634e.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=glenng@NetEffect.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).