From: Stephen Hemminger <shemminger@vyatta.com>
To: Guo-Fu Tseng <cooldavid@cooldavid.org>
Cc: Jeff Garzik <jgarzik@pobox.com>, Ethan <ethanhsiao@jmicron.com>,
akeemting <akeem@jmicron.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH netdev-2.6] jme: JMicron Gigabit Ethernet Driver (Resend1)
Date: Sat, 23 Aug 2008 14:40:40 -0400 [thread overview]
Message-ID: <20080823144040.08fcc322@speedy> (raw)
In-Reply-To: <48B04DF4.3080103@cooldavid.org>
A couple of really minor things that could be changed (but don't have to).
> +struct jme_spi_op {
> + void __user *uwbuf;
> + void __user *urbuf;
> + __u8 wn; /* Number of write actions */
> + __u8 rn; /* Number of read actions */
> + __u8 bitn; /* Number of bits per action */
> + __u8 spd; /* The maxim acceptable speed of controller, in MHz.*/
> + __u8 mode; /* CPOL, CPHA, and Duplex mode of SPI */
> +
> + /* Internal use only */
> + __u8 *kwbuf;
> + __u8 *krbuf;
> + __u8 sr;
> + __u16 halfclk; /* Half of clock cycle calculated from spd, in ns */
> +};
The conventional usage is to use __u8 for parameters that are being used in a kernel to
user ABI interface (like ioctl), and u8 for elements in a structure in a device driver.
Not sure why there is a distinction, but that is what I learne.
> --- netdev-2.6/include/linux/pci_ids.h 2008-08-22 07:48:54.000000000 +0800
> +++ linux/include/linux/pci_ids.h 2008-08-23 01:12:07.000000000 +0800
> @@ -2224,6 +2224,8 @@
> #define PCI_DEVICE_ID_JMICRON_JMB38X_SD 0x2381
> #define PCI_DEVICE_ID_JMICRON_JMB38X_MMC 0x2382
> #define PCI_DEVICE_ID_JMICRON_JMB38X_MS 0x2383
> +#define PCI_DEVICE_ID_JMICRON_JMC250 0x0250
> +#define PCI_DEVICE_ID_JMICRON_JMC260 0x0260
Most device drivers no longer add entries to pci_ids.h for each device type. This used to
be done, but the file was getting too big and the id's only get used in one place.
prev parent reply other threads:[~2008-08-23 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 17:50 [PATCH netdev-2.6] jme: JMicron Gigabit Ethernet Driver (Resend1) Guo-Fu Tseng
2008-08-23 18:40 ` Stephen Hemminger [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=20080823144040.08fcc322@speedy \
--to=shemminger@vyatta.com \
--cc=akeem@jmicron.com \
--cc=cooldavid@cooldavid.org \
--cc=ethanhsiao@jmicron.com \
--cc=jgarzik@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.