From: Jeff Garzik <jgarzik@pobox.com>
To: Guo-Fu Tseng <cooldavid@cooldavid.org>
Cc: Ethan <ethanhsiao@jmicron.com>, akeemting <akeem@jmicron.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH netdev-2.6] jme: JMicron Gigabit Ethernet Driver
Date: Sat, 23 Aug 2008 02:41:59 -0400 [thread overview]
Message-ID: <48AFB137.9020506@pobox.com> (raw)
In-Reply-To: <48AFA8A8.6070604@cooldavid.org>
Guo-Fu Tseng wrote:
> Hi, Jeff:
>
> Here is the full patch of JMicron Gigabit Ethernet driver.
> Supporting JMC250, and JMC260.
>
> I'm new in this submitting system, I've tried hard not to done silly
> errors.
> Comments, and corrections are welcome from anyone. Thank you for
> reviewing it.
>
> The patch is also available at:
> http://cooldavid.org/download/jme.netdev-2.6.20080823.patch
>
> Signed-off-by: Guo-Fu Tseng <cooldavid@cooldavid.org>
Very nice and clean and feature-complete! Comments:
* the definition of jwrite32() and jread32(): writel() and readl() are
defined in terms of the little-endian PCI bus, and therefore
automatically handle byteswapping (or not) as defined by the platform API.
You should be able to just remove those le32_to_cpu() and the reverse,
to obtain proper behavior.
* The atomic values rx_cleaning and tx_cleaning look problematic and
potentially racy, though I admit not having completely evaluated its usage.
* we prefer not to add custom ioctls, but rather add functionality to
ethtool. in particular, JMESPIIOCTL does not appear to have any
security checks, and is a potential security hole that permits an
unpriveleged user direct access to hardware
next prev parent reply other threads:[~2008-08-23 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 6:05 [PATCH netdev-2.6] jme: JMicron Gigabit Ethernet Driver Guo-Fu Tseng
2008-08-23 6:41 ` Jeff Garzik [this message]
2008-08-23 16:04 ` Guo-Fu Tseng
2008-08-25 16:21 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2008-09-15 17:00 Guo-Fu Tseng
2008-09-16 2:47 ` Ethan
2008-09-18 16:07 ` Jeff Garzik
2008-11-21 5:20 ` Stephen Hemminger
2008-11-21 5:36 ` David Miller
2008-11-21 6:45 ` Stephen Hemminger
2008-11-21 8:46 ` David Miller
2008-11-21 16:22 ` Guo-Fu Tseng
2008-11-21 16:18 ` Guo-Fu Tseng
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=48AFB137.9020506@pobox.com \
--to=jgarzik@pobox.com \
--cc=akeem@jmicron.com \
--cc=cooldavid@cooldavid.org \
--cc=ethanhsiao@jmicron.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).