Netdev List
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Ron Mercer <ron.mercer@qlogic.com>
Cc: netdev@vger.kernel.org, linux-driver@qlogic.com,
	Ying Ping Lok <ying.lok@qlogic.com>,
	Mike Metskas <mike.metskas@qlogic.com>
Subject: Re: [RFC] new qla3xxx NIC Driver v2.02.00k19
Date: Wed, 17 May 2006 01:23:46 +0200	[thread overview]
Message-ID: <20060516232346.GA20608@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <0BB3E5E7462EEA4295BC02D49691DC070D32F3@AVEXCH1.qlogic.org>

Ron Mercer <ron.mercer@qlogic.com> :
[...]
> Looking forward to any and all feedback.

First pass:
- please reorder the code so that the forward declarations are not needed
- the typedefs (say PQL3XXX_PORT_REGISTERS) hide pointer information.
  They are useless (and capitalized :o/ ). Just say no to typedef.
- the debug functions abuse copy/paste. Please use struct array + loop
  if you really want these to stay.
- "return" is not a function. It does not need parenthesis.
- 80 colums disease in ql_link_state_machine. The indentation is terrible.
- label for goto should be at the start of the line.
- acquire_adapter_lock must go. Conditional locking is a pain to maintain.
- the error path in ql3xxx_probe is broken. Use named _and_ numbered
  goto if you want to avoid it (i.e. "goto err_undo_something_1" then
  "goto err_undo_something_else_2", etc.).
- ql_set_ethtool_ops() is useless bloat. Please remove.
- QL_LOCK_DRVR_WAIT should be a function, not a macro
- the status code should be propagated (request_irq, pci_enable_device,
  pci_request_regions, etc.).
- no __iomem, __u32, __le32 ? Seems strange.
- replace return (0) with NETDEV_TX_OK in ql3xxx_send
  (and s/send/start_xmit/ ?).

-- 
Ueimor

      reply	other threads:[~2006-05-16 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 17:52 [RFC] new qla3xxx NIC Driver v2.02.00k19 Ron Mercer
2006-05-16 23:23 ` Francois Romieu [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=20060516232346.GA20608@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=linux-driver@qlogic.com \
    --cc=mike.metskas@qlogic.com \
    --cc=netdev@vger.kernel.org \
    --cc=ron.mercer@qlogic.com \
    --cc=ying.lok@qlogic.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