From: David Miller <davem@davemloft.net>
To: dm@chelsio.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/7] cxgb4: new driver submission
Date: Wed, 17 Feb 2010 17:59:27 -0800 (PST) [thread overview]
Message-ID: <20100217.175927.88022884.davem@davemloft.net> (raw)
In-Reply-To: <1266457062-31150-1-git-send-email-dm@chelsio.com>
From: Dimitris Michailidis <dm@chelsio.com>
Date: Wed, 17 Feb 2010 17:37:35 -0800
>
> The following 7 patches add a new driver cxgb4 for Chelsio's new 1G and 10G
> cards. At this time this is for review and comments, I'll be sending an
> updated patch series once any review comments are incorporated.
There is lots of trailing whitespace added by your changes.
There's also a case of spaces followed by tab characters in
the initial indentation of lines.
What makes those two things so incredibly inexcusable is that the very
tools we use to add changes to the tree _tell_ you about these things.
bundle-895.mbox:6829: trailing whitespace.
FW_STAT_TX_PORT_FRAMES_IX,
bundle-895.mbox:6879: trailing whitespace.
FW_STAT_RX_PORT_PPP7_IX,
bundle-895.mbox:6985: trailing whitespace.
FW_STAT_LB_PORT_FRAMES_IX,
bundle-895.mbox:6986: trailing whitespace.
FW_STAT_LB_PORT_BCAST_IX,
bundle-895.mbox:9918: trailing whitespace.
int ret;
bundle-895.mbox:10135: space before tab in indent.
if (mac) {
bundle-895.mbox:12533: trailing whitespace.
* prevent further unmapping attempts.
bundle-895.mbox:18605: trailing whitespace.
bundle-895.mbox:18981: trailing whitespace.
dev_info(adap->pdev_dev,
bundle-895.mbox:19266: trailing whitespace.
fatal: 10 lines add whitespace errors.
Such automated clerical issues should be taken care of before you even
submit this for "review". It's the same as making sure the code
compiles.
Also you should use the netdev_*() message logging helpers added
by Joe Perches instead of your local CMSG_*() hacks.
Finally, this V_*, S_*, F_* naming scheme for register values is
backwards and if anything very non-standard. Please use normal macro
names for these things so you code is more readable by people who
have to look at all of the other device drivers in the tree not
just your's.
next prev parent reply other threads:[~2010-02-18 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 1:37 [PATCH net-next 0/7] cxgb4: new driver submission Dimitris Michailidis
2010-02-18 1:37 ` [PATCH net-next 1/7] cxgb4: Add register and message definitions Dimitris Michailidis
2010-02-18 1:37 ` [PATCH net-next 2/7] cxgb4: Add FW API definitions Dimitris Michailidis
2010-02-18 1:37 ` [PATCH net-next 3/7] cxgb4: Add HW and FW support code Dimitris Michailidis
2010-02-18 1:37 ` [PATCH net-next 4/7] cxgb4: Add packet queues and packet DMA code Dimitris Michailidis
2010-02-18 1:37 ` [PATCH net-next 5/7] cxgb4: Add remaining driver headers and L2T management Dimitris Michailidis
2010-02-18 1:37 ` [PATCH net-next 6/7] cxgb4: Add main driver file and driver Makefile Dimitris Michailidis
2010-02-18 1:37 ` [PATCH net-next 7/7] net: Hook up cxgb4 to Kconfig and Makefile Dimitris Michailidis
2010-02-18 1:59 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-18 2:56 [PATCH net-next 0/7] cxgb4: new driver submission Dimitrios Michailidis
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=20100217.175927.88022884.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dm@chelsio.com \
--cc=netdev@vger.kernel.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).