From: Bill Fink <billfink@mindspring.com>
To: "Subbu Seetharaman" <subbus@serverengines.com>
Cc: jeff@garzik.org, netdev@vger.kernel.org
Subject: Re: [PATCH 8/8] benet: Kconfig, Makefile, MAINTAINERS
Date: Sat, 5 Jul 2008 01:39:33 -0400 [thread overview]
Message-ID: <20080705013933.91175119.billfink@mindspring.com> (raw)
In-Reply-To: <20080704165755.1c3a284c@mailhost.serverengines.com>
On Fri, 04 Jul 2008, Subbu Seetharaman wrote:
> Signed-off-by: Subbu Seetharaman <subbus@serverengines.com>
> ---
> MAINTAINERS | 7 +++++++
> drivers/net/Kconfig | 8 ++++++++
> drivers/net/Makefile | 1 +
> 3 files changed, 16 insertions(+), 0 deletions(-)
...
> diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
> index f4182cf..78b4d6e 100644
> --- a/drivers/net/Kconfig
> +++ b/drivers/net/Kconfig
> @@ -2581,6 +2581,14 @@ config BNX2X
>
> source "drivers/net/sfc/Kconfig"
>
> +config BENET
> + tristate "ServerEngines 10Gb NIC - BladeEngine"
> + depends on PCI
> + select INET_LRO
> + help
> + This driver implements the NIC functionality for ServerEngines
> + 10Gb network adapter BladeEngine (EC 3210).
> +
> endif # NETDEV_10000
>
> source "drivers/net/tokenring/Kconfig"
I'm no Kconfig expert, but based on previous driver discussions,
I believe the above depends needs to be changed to:
depends on PCI && INET
to prevent certain build problems that can arise from having just
the "select INET_LRO" clause.
-Bill
next prev parent reply other threads:[~2008-07-05 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 16:57 [PATCH 8/8] benet: Kconfig, Makefile, MAINTAINERS Subbu Seetharaman
2008-07-05 5:39 ` Bill Fink [this message]
2008-07-06 17:41 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2008-07-07 13:57 Jeff Garzik
2008-07-09 1:55 Subbu Seetharaman
2008-07-23 10:27 Subbu Seetharaman
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=20080705013933.91175119.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=subbus@serverengines.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;
as well as URLs for NNTP newsgroup(s).