From: Harald Welte <laforge@gnumonks.org>
To: David Miller <davem@redhat.com>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: [PATCH] fix HIPQUAD macro in kernel.h
Date: Thu, 8 Aug 2002 13:31:12 +0200 [thread overview]
Message-ID: <20020808133112.E11828@sunbeam.de.gnumonks.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
Hi Dave!
Below is a fix for the HIPQUAD macro in kernel.h. The macro is currently
not endian-aware - it just assumes running on a little-endian machine.
If you don't like the #ifdefs in kernel.h, the macros could be moved into
include/linux/byteorder/.
Please apply, thanks
--- linux-2.4.19-rc5-plain/include/linux/kernel.h Wed Aug 7 22:55:03 2002
+++ linux-2.4.19-rc5-endian/include/linux/kernel.h Thu Aug 8 11:34:13 2002
@@ -12,6 +12,7 @@
#include <linux/stddef.h>
#include <linux/types.h>
#include <linux/compiler.h>
+#include <asm/byteorder.h>
/* Optimization barrier */
/* The "volatile" is due to gcc bugs */
@@ -128,11 +129,17 @@
((unsigned char *)&addr)[2], \
((unsigned char *)&addr)[3]
+#if defined(__LITTLE_ENDIAN)
#define HIPQUAD(addr) \
((unsigned char *)&addr)[3], \
((unsigned char *)&addr)[2], \
((unsigned char *)&addr)[1], \
((unsigned char *)&addr)[0]
+#elif defined(__BIG_ENDIAN)
+#define HIPQUAD NIPQUAD
+#else
+#error "Please fix asm/byteorder.h"
+#endif /* __LITTLE_ENDIAN */
/*
* min()/max() macros that also do
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org/
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M+
V-- PS++ PE-- Y++ PGP++ t+ 5-- !X !R tv-- b+++ !DI !D G+ e* h--- r++ y+(*)
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-08-08 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 11:31 Harald Welte [this message]
2002-08-08 11:41 ` Andi Kleen
2002-08-08 12:06 ` Harald Welte
2002-08-08 14:48 ` David S. Miller
2002-08-08 14:58 ` David S. Miller
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=20020808133112.E11828@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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
all inboxes | Powered by JetHome®