From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arch <linux-arch@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>,
"tony.luck" <tony.luck@intel.com>
Subject: [PATCHv4 6/6] byteorder: add copy_{endian} helpers
Date: Mon, 02 Jun 2008 10:37:24 -0700 [thread overview]
Message-ID: <1212428244.11008.40.camel@brick> (raw)
Add helpers for the idiom:
*(__le16 *)ptr = cpu_to_le16(val);
Can now be written as:
copy_le16(ptr, val);
Implemented as macros to allow val to be byteswapped at compile-time
when it is a constant.
Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
---
include/linux/byteorder.h | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/include/linux/byteorder.h b/include/linux/byteorder.h
index b4713ce..8d3c847 100644
--- a/include/linux/byteorder.h
+++ b/include/linux/byteorder.h
@@ -278,6 +278,17 @@ static inline __be64 __cpu_to_be64p(const __u64 *p)
# define htons(x) ___htons(x)
# define ntohs(x) ___ntohs(x)
+/*
+ * Defined as macros to allow constant folding of the cpu_to_XXXX when
+ * possible.
+ */
+#define copy_le16(ptr, val) (*(__le16 *)(ptr) = cpu_to_le16((u16)(val));)
+#define copy_le32(ptr, val) (*(__le32 *)(ptr) = cpu_to_le32((u32)(val));)
+#define copy_le64(ptr, val) (*(__le64 *)(ptr) = cpu_to_le64((u64)(val));)
+#define copy_be16(ptr, val) (*(__be16 *)(ptr) = cpu_to_be16((u16)(val));)
+#define copy_be32(ptr, val) (*(__be32 *)(ptr) = cpu_to_be32((u32)(val));)
+#define copy_be64(ptr, val) (*(__be64 *)(ptr) = cpu_to_be64((u64)(val));)
+
static inline void le16_add_cpu(__le16 *var, u16 val)
{
*var = cpu_to_le16(le16_to_cpup(var) + val);
--
1.5.6.rc0.277.g804cf
next reply other threads:[~2008-06-02 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 17:37 Harvey Harrison [this message]
2008-06-02 19:15 ` [PATCHv4 6/6] byteorder: add copy_{endian} helpers Geert Uytterhoeven
2008-06-04 18:38 ` Harvey Harrison
2008-06-04 19:34 ` Geert Uytterhoeven
2008-06-04 19:39 ` Harvey Harrison
2008-06-04 23:20 ` Russell King
2008-06-04 23:27 ` Harvey Harrison
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=1212428244.11008.40.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=tony.luck@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