From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
ocfs2-devel@oss.oracle.com
Subject: Re: [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to
Date: Mon, 31 Dec 2007 20:05:22 +0000 [thread overview]
Message-ID: <20071231200519.GA10232@joi> (raw)
In-Reply-To: <20071231193801.GS13821@ca-server1.us.oracle.com>
On Mon, Dec 31, 2007 at 11:38:01AM -0800, Mark Fasheh wrote:
> On Sun, Dec 30, 2007 at 08:06:34PM +0100, Marcin Slusarz wrote:
> > There are many places where these functions would be useful.
> > (just look at: grep -r 'cpu_to_[ble12346]*([ble12346]*_to_cpu.*[-+]' linux-src/)
> > What do you think?
> >
> > ps: this patch depends on http://lkml.org/lkml/2007/12/25/35
> > --
> >
> > add inline functions which add native byte order variable to
> > little/big endian variable to core header and as an example
> > convert ext3 to use them
>
> You might want to note where you got these functions from in your message.
Yes, my mistake, sorry about that.
> Also, it would be easier to follow these changes if you had broken things up
> into two patches - one which moved stuff from ocfs2 into generic helpers and
> a 2nd one to convert ext3.
Will do (tomorrow).
> Looking into my crystal ball, I see a bunch of "convert to using byteorder
> math macros" patches coming down the pipe. Since we're talking about disk
> fields where a mistake could be costly, I suggest that any patch more than a
> couple of lines should be tested by the submitter with sparse. A statement
> that sparse didn't produce any new warnings (with the patch applied) could
> be included in the description.
Good idea. Thanks.
Marcin
WARNING: multiple messages have this Message-ID (diff)
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to core
Date: Mon, 31 Dec 2007 20:04:02 -0000 [thread overview]
Message-ID: <20071231200519.GA10232@joi> (raw)
In-Reply-To: <20071231193801.GS13821@ca-server1.us.oracle.com>
On Mon, Dec 31, 2007 at 11:38:01AM -0800, Mark Fasheh wrote:
> On Sun, Dec 30, 2007 at 08:06:34PM +0100, Marcin Slusarz wrote:
> > There are many places where these functions would be useful.
> > (just look at: grep -r 'cpu_to_[ble12346]*([ble12346]*_to_cpu.*[-+]' linux-src/)
> > What do you think?
> >
> > ps: this patch depends on http://lkml.org/lkml/2007/12/25/35
> > --
> >
> > add inline functions which add native byte order variable to
> > little/big endian variable to core header and as an example
> > convert ext3 to use them
>
> You might want to note where you got these functions from in your message.
Yes, my mistake, sorry about that.
> Also, it would be easier to follow these changes if you had broken things up
> into two patches - one which moved stuff from ocfs2 into generic helpers and
> a 2nd one to convert ext3.
Will do (tomorrow).
> Looking into my crystal ball, I see a bunch of "convert to using byteorder
> math macros" patches coming down the pipe. Since we're talking about disk
> fields where a mistake could be costly, I suggest that any patch more than a
> couple of lines should be tested by the submitter with sparse. A statement
> that sparse didn't produce any new warnings (with the patch applied) could
> be included in the description.
Good idea. Thanks.
Marcin
WARNING: multiple messages have this Message-ID (diff)
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
ocfs2-devel@oss.oracle.com
Subject: Re: [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to core
Date: Mon, 31 Dec 2007 21:05:22 +0100 [thread overview]
Message-ID: <20071231200519.GA10232@joi> (raw)
In-Reply-To: <20071231193801.GS13821@ca-server1.us.oracle.com>
On Mon, Dec 31, 2007 at 11:38:01AM -0800, Mark Fasheh wrote:
> On Sun, Dec 30, 2007 at 08:06:34PM +0100, Marcin Slusarz wrote:
> > There are many places where these functions would be useful.
> > (just look at: grep -r 'cpu_to_[ble12346]*([ble12346]*_to_cpu.*[-+]' linux-src/)
> > What do you think?
> >
> > ps: this patch depends on http://lkml.org/lkml/2007/12/25/35
> > --
> >
> > add inline functions which add native byte order variable to
> > little/big endian variable to core header and as an example
> > convert ext3 to use them
>
> You might want to note where you got these functions from in your message.
Yes, my mistake, sorry about that.
> Also, it would be easier to follow these changes if you had broken things up
> into two patches - one which moved stuff from ocfs2 into generic helpers and
> a 2nd one to convert ext3.
Will do (tomorrow).
> Looking into my crystal ball, I see a bunch of "convert to using byteorder
> math macros" patches coming down the pipe. Since we're talking about disk
> fields where a mistake could be costly, I suggest that any patch more than a
> couple of lines should be tested by the submitter with sparse. A statement
> that sparse didn't produce any new warnings (with the patch applied) could
> be included in the description.
Good idea. Thanks.
Marcin
next prev parent reply other threads:[~2007-12-31 20:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 19:06 [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to core Marcin Slusarz
2007-12-30 19:06 ` Marcin Slusarz
2007-12-30 19:18 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to Christoph Hellwig
2007-12-30 19:18 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to core Christoph Hellwig
2007-12-30 21:49 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to Marcin Slusarz
2007-12-30 21:49 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to core Marcin Slusarz
2007-12-31 9:17 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to Christoph Hellwig
2007-12-31 9:17 ` [Ocfs2-devel] [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to core Christoph Hellwig
2007-12-31 9:17 ` Christoph Hellwig
2007-12-31 11:43 ` [Ocfs2-devel] " Mark Fasheh
2007-12-31 19:41 ` Mark Fasheh
2007-12-31 19:41 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to Mark Fasheh
2007-12-31 11:39 ` [Ocfs2-devel] Re: [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to core Mark Fasheh
2007-12-31 19:38 ` Mark Fasheh
2007-12-31 19:38 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to Mark Fasheh
2007-12-31 20:04 ` Marcin Slusarz [this message]
2007-12-31 20:05 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to core Marcin Slusarz
2007-12-31 20:05 ` [RFC][PATCH] byteorder: introduce le32_add_cpu & friends to 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=20071231200519.GA10232@joi \
--to=marcin.slusarz@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.