All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
	linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: use proper little-endian bitops
Date: Tue, 31 May 2011 16:07:02 -0700	[thread overview]
Message-ID: <20110531230702.GE31742@noexit.corp.google.com> (raw)
In-Reply-To: <20110531225713.GA10985@wotan.suse.de>

On Tue, May 31, 2011 at 03:57:13PM -0700, Mark Fasheh wrote:
> On Mon, May 30, 2011 at 09:58:05PM +0900, Akinobu Mita wrote:
> > Using __test_and_{set,clear}_bit_le() with ignoring its return value
> > can be replaced with __{set,clear}_bit_le().
> > 
> > Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> > Cc: Joel Becker <jlbec@evilplan.org>
> > Cc: Mark Fasheh <mfasheh@suse.com>
> > Cc: ocfs2-devel at oss.oracle.com
> 
> Looks reasonable to me...
> 
> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
> 
> Joel?

	No argument here.  Akinobu, do you want me to send it with ocfs2
fixes, or are you going to push it along?

Acked-by: Joel Becker <jlbec@evilplan.org>

Joel

-- 

"Lately I've been talking in my sleep.
 Can't imagine what I'd have to say.
 Except my world will be right
 When love comes back my way."

			http://www.jlbec.org/
			jlbec at evilplan.org

WARNING: multiple messages have this Message-ID (diff)
From: Joel Becker <jlbec@evilplan.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
	linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH] ocfs2: use proper little-endian bitops
Date: Tue, 31 May 2011 16:07:02 -0700	[thread overview]
Message-ID: <20110531230702.GE31742@noexit.corp.google.com> (raw)
In-Reply-To: <20110531225713.GA10985@wotan.suse.de>

On Tue, May 31, 2011 at 03:57:13PM -0700, Mark Fasheh wrote:
> On Mon, May 30, 2011 at 09:58:05PM +0900, Akinobu Mita wrote:
> > Using __test_and_{set,clear}_bit_le() with ignoring its return value
> > can be replaced with __{set,clear}_bit_le().
> > 
> > Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> > Cc: Joel Becker <jlbec@evilplan.org>
> > Cc: Mark Fasheh <mfasheh@suse.com>
> > Cc: ocfs2-devel@oss.oracle.com
> 
> Looks reasonable to me...
> 
> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
> 
> Joel?

	No argument here.  Akinobu, do you want me to send it with ocfs2
fixes, or are you going to push it along?

Acked-by: Joel Becker <jlbec@evilplan.org>

Joel

-- 

"Lately I've been talking in my sleep.
 Can't imagine what I'd have to say.
 Except my world will be right
 When love comes back my way."

			http://www.jlbec.org/
			jlbec@evilplan.org

  reply	other threads:[~2011-05-31 23:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 12:58 [Ocfs2-devel] [PATCH] ocfs2: use proper little-endian bitops Akinobu Mita
2011-05-30 12:58 ` Akinobu Mita
2011-05-31 22:57 ` [Ocfs2-devel] " Mark Fasheh
2011-05-31 22:57   ` Mark Fasheh
2011-05-31 23:07   ` Joel Becker [this message]
2011-05-31 23:07     ` Joel Becker
2011-05-31 23:52     ` [Ocfs2-devel] " Akinobu Mita
2011-05-31 23:52       ` Akinobu Mita
2011-06-01  2:24 ` [Ocfs2-devel] " Joel Becker
2011-06-01  2:24   ` Joel Becker

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=20110531230702.GE31742@noexit.corp.google.com \
    --to=jlbec@evilplan.org \
    --cc=akinobu.mita@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.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.