From: Stephen Hemminger <shemminger@osdl.org>
To: Ayaz Abdulla <aabdulla@nvidia.com>,
Manfred Spraul <manfred@colorfullife.com>,
Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>, netdev@vger.kernel.org
Subject: [PATCH 2/3] forcedeth: le32 annotation
Date: Thu, 27 Jul 2006 18:50:09 -0700 [thread overview]
Message-ID: <20060728015054.393160616@localhost> (raw)
In-Reply-To: 20060728015007.625581647@localhost
[-- Attachment #1: forcedeth-types.patch --]
[-- Type: text/plain, Size: 873 bytes --]
Use __le32 to indicate byte order of hardware ring elements
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
drivers/net/forcedeth.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
--- linux-2.6.orig/drivers/net/forcedeth.c 2006-07-27 17:43:52.000000000 -0700
+++ linux-2.6/drivers/net/forcedeth.c 2006-07-27 17:44:49.000000000 -0700
@@ -381,15 +381,15 @@
/* Big endian: should work, but is untested */
struct ring_desc {
- u32 buf;
- u32 flaglen;
+ __le32 buf;
+ __le32 flaglen;
};
struct ring_desc_ex {
- u32 bufhigh;
- u32 buflow;
- u32 txvlan;
- u32 flaglen;
+ __le32 bufhigh;
+ __le32 buflow;
+ __le32 txvlan;
+ __le32 flaglen;
};
union ring_type {
@@ -653,8 +653,8 @@
};
struct register_test {
- u32 reg;
- u32 mask;
+ __le32 reg;
+ __le32 mask;
};
static const struct register_test nv_registers_test[] = {
--
next prev parent reply other threads:[~2006-07-28 1:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 1:50 [PATCH 0/3] forcedeth: patches Stephen Hemminger
2006-07-28 1:50 ` [PATCH 1/3] forcedeth: coding style cleanups Stephen Hemminger
2006-07-29 5:29 ` Jeff Garzik
2006-07-28 1:50 ` Stephen Hemminger [this message]
2006-07-28 1:50 ` [PATCH 3/3] forcdeth: NAPI support (rev3) Stephen Hemminger
2006-07-28 2:01 ` [PATCH 4/3] forcedeth: fix NAPI hang in IRQ Stephen Hemminger
2006-07-29 4:10 ` Andrew Morton
2006-07-29 5:30 ` [PATCH 3/3] forcdeth: NAPI support (rev3) Jeff Garzik
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=20060728015054.393160616@localhost \
--to=shemminger@osdl.org \
--cc=aabdulla@nvidia.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=manfred@colorfullife.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.