Use __le32 to indicate byte order of hardware ring elements
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
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[] = {
--
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
