From: Mark Fasheh <mark.fasheh@oracle.com>
To: marcin.slusarz@gmail.com
Cc: kernel-janitors <kernel-janitors@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
xfs-masters@oss.sgi.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org,
OCFS2-devel <ocfs2-devel@oss.oracle.com>
Subject: Re: [PATCH 1/3] byteorder: move le32_add_cpu & friends from OCFS2 to core
Date: Sun, 6 Jan 2008 12:50:55 -0800 [thread overview]
Message-ID: <20080106205055.GR23506@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1199547382-29969-2-git-send-email-marcin.slusarz@gmail.com>
On Sat, Jan 05, 2008 at 04:36:20PM +0100, marcin.slusarz@gmail.com wrote:
> - move inline functions which add native byte order variable to
> little/big endian variable to core header
> * le16_add_cpu(__le16 *var, u16 val)
> * le32_add_cpu(__le32 *var, u32 val)
> * le64_add_cpu(__le64 *var, u64 val)
> * be32_add_cpu(__be32 *var, u32 val)
> - add for completeness:
> * be16_add_cpu(__be16 *var, u16 val)
> * be64_add_cpu(__be64 *var, u64 val)
>
> Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
Acked-by: Mark Fasheh <mark.fasheh@oracle.com>
--
Mark Fasheh
Principal Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2008-01-06 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 15:36 [PATCH 0/3] byteorder: introduce le32_add_cpu & friends to core marcin.slusarz
2008-01-05 15:36 ` [PATCH 1/3] byteorder: move le32_add_cpu & friends from OCFS2 " marcin.slusarz
2008-01-06 20:50 ` Mark Fasheh [this message]
2008-01-05 15:36 ` [PATCH 2/3] ext3: replace all adds to little endians variables with le*_add_cpu marcin.slusarz
2008-01-05 15:36 ` [PATCH 3/3] xfs: convert beX_add to beX_add_cpu (new common API) marcin.slusarz
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=20080106205055.GR23506@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=xfs-masters@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