From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Mike Phillips <mikep@linuxtr.net>
Cc: Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] New driver 3Com 3C359 Tokenring Velocity XL
Date: Wed, 20 Feb 2002 11:32:05 -0500 [thread overview]
Message-ID: <3C73CF85.E3DA3943@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10202181451060.4149-100000@www.linuxtr.net>
Thanks, applied to 2.4 and 2.5. I removed the definition of
PCI_DEVICE_xxx from the top of 3c359.h...
Comments:
1) buggy use of PCI DMA API -- you should use memory returned from
pci_alloc_consistent, do not directly map memory created by
alloc_trdev() nor depend on the alignment returned by alloc_trdev()
2) support for ETHTOOL_GDRVINFO ioctl
3) support for ETHTOOL_[GS]MSGLVL ioctls... this implies that
'message_level' would only serve as a default for a value that can be
changed per-interface
4) ideally "\n" should not be in MODULE_DESCRIPTION
5) style: no need to cast to/from a void pointer, such as
> struct xl_private *xl_priv = (struct xl_private *)dev->priv ;
6) hardcoded magic numbers for PKT_BUF_SZ limits (100 and 18000)
7) xl_probe duplicates error handling code... use the standard kernel
style of multiple goto targets, one for each needed stage of
cleanup-after-error:
err_out3:
pci_release_regions(pdev)
err_out2:
kfree(dev)
err_out:
return rc;
8) in xl_hw_reset, you probably want to call yield [in 2.5] or
schedule_timeout
9) jiffies comparison bug: never directly compare jiffies, use
time_before() or time_after()
10) in xl_open, return the error value returned by request_irq, on error
11) same comment for xl_open as #7
12) xl_wait_misr_flags needs to call yield() or -something-, don't just
empty loop. cpu_relax(), for example, if you cannot schedule...
Overall... good job, it's a readable, clean driver.
Jeff
--
Jeff Garzik | "Why is it that attractive girls like you
Building 1024 | always seem to have a boyfriend?"
MandrakeSoft | "Because I'm a nympho that owns a brewery?"
| - BBC TV show "Coupling"
next prev parent reply other threads:[~2002-02-20 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 20:58 [PATCH] New driver 3Com 3C359 Tokenring Velocity XL Mike Phillips
2002-02-20 16:32 ` Jeff Garzik [this message]
2002-02-21 2:20 ` Mike Phillips
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=3C73CF85.E3DA3943@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikep@linuxtr.net \
/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