From: Peter Foley <pefoley2@pefoley.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Foley <pefoley2@pefoley.com>,
rdunlap@infradead.org, linux-doc@vger.kernel.org,
sudeep.dutt@intel.com, nikhil.rao@intel.com,
ashutosh.dixit@intel.com, akpm@linux-foundation.org,
gregkh@linuxfoundation.org
Subject: [PATCH] tools: add more endian.h macros
Date: Tue, 23 Sep 2014 18:50:53 -0400 [thread overview]
Message-ID: <1411512653-17093-1-git-send-email-pefoley2@pefoley.com> (raw)
Add some more macros to tools/endian.h to allow mpssd to be compiled
against glibc < 2.9.
Signed-off-by: Peter Foley <pefoley2@pefoley.com>
Cc: rdunlap@infradead.org
Cc: linux-doc@vger.kernel.org
Cc: sudeep.dutt@intel.com
Cc: nikhil.rao@intel.com
Cc: ashutosh.dixit@intel.com
Cc: akpm@linux-foundation.org
Cc: gregkh@linuxfoundation.org
---
tools/include/tools/endian.h | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/tools/include/tools/endian.h b/tools/include/tools/endian.h
index 5d42e20..8001194 100644
--- a/tools/include/tools/endian.h
+++ b/tools/include/tools/endian.h
@@ -15,6 +15,18 @@
#define htole64(x) (x)
#endif
+#ifndef le16toh
+#define le16toh(x) (x)
+#endif
+
+#ifndef le32toh
+#define le32toh(x) (x)
+#endif
+
+#ifndef le64toh
+#define le64toh(x) (x)
+#endif
+
#else /* __BYTE_ORDER */
#ifndef htole16
@@ -27,6 +39,18 @@
#define htole64(x) __bswap_64(x)
#endif
+#ifndef le16toh
+#define le16toh(x) __bswap_16(x)
+#endif
+
+#ifndef le32toh
+#define le32toh(x) __bswap_32(x)
+#endif
+
+#ifndef le64toh
+#define le64toh(x) __bswap_64(x)
+#endif
+
#endif
#endif /* _TOOLS_ENDIAN_H */
--
2.1.1
next reply other threads:[~2014-09-23 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 22:50 Peter Foley [this message]
2014-09-25 17:37 ` Randy Dunlap
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=1411512653-17093-1-git-send-email-pefoley2@pefoley.com \
--to=pefoley2@pefoley.com \
--cc=akpm@linux-foundation.org \
--cc=ashutosh.dixit@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=rdunlap@infradead.org \
--cc=sudeep.dutt@intel.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®