From: David Miller <davem@davemloft.net>
To: rmody@brocade.com
Cc: netdev@vger.kernel.org, amathur@brocade.com
Subject: Re: Subject: [PATCH 1/9] bna: Brocade 10Gb Ethernet device driver
Date: Fri, 28 Aug 2009 23:18:21 -0700 (PDT) [thread overview]
Message-ID: <20090828.231821.228158617.davem@davemloft.net> (raw)
In-Reply-To: <200908290518.n7T5IdjW031875@blc-10-10.brocade.com>
You're going to have to remove all of the
__ESX_COS__, __VMKERNEL_MODULE__, __VMKNETDDI_QUEUEOPS__
ifdef tests and protected code in this driver.
Nothing sets those CPP defines, and the Linux kernel is not
a place where you can maintain your compatability code for
building the driver in other environments.
Next, you have defined your own implementation of a driver
debug logging facility, when we have a generic one already
for network drivers via netif_msg_*() and associated
NETIF_MSG_* debugging masks. See other drivers for details.
If it doesn't fully suit your needs, fix the existing
facilities to do so.
These are just the most obvious things I noticed by glancing
quickly at your driver. I'm sure there a many other things
you will need to fix up before we can add your driver.
The code is 1MB in size, which almost guarentees there are lots of
things which will need to be removed :-) Even the largest 10GB drivers
with tons of firmware are ~500K in size and I even consider that
bordering on excessive.
prev parent reply other threads:[~2009-08-29 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 5:18 Subject: [PATCH 1/9] bna: Brocade 10Gb Ethernet device driver Rasesh Mody
2009-08-29 6:18 ` David Miller [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=20090828.231821.228158617.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amathur@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.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