All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH -v2] gfs2: fix bitmap declaration
Date: Thu, 07 Mar 2013 16:06:39 +0000	[thread overview]
Message-ID: <1362672399.2528.32.camel@menhir> (raw)
In-Reply-To: <CAC5umyjw3xzdExvf3TA6i3iH=ortPeJivetUpEyCP5Mzmn6wEg@mail.gmail.com>

Hi,

On Thu, 2013-03-07 at 23:38 +0900, Akinobu Mita wrote:
> 2013/3/7 Steven Whitehouse <swhiteho@redhat.com>:
> > Hi,
> >
> > This doesn't apply over the patch which Dave just sent. Can you redo
> > this against the current GFS2 -nmw tree if it is still required? Thanks,
> 
> I checked Dave's patch.  It fixes the same issue that I was trying to fix.
> So this -v2 patch is not needed anymore.
> 
> But the cleanup patch in v1 ([PATCH 2/2] gfs2: use memchr_inv) is still
> applicable. So I'll resend it soon.

Ok, thanks. I've pushed the memchr_inv patch into the -nmw git tree,

Steve.




WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	cluster-devel@redhat.com,
	Christine Caulfield <ccaulfie@redhat.com>,
	David Teigland <teigland@redhat.com>
Subject: Re: [PATCH -v2] gfs2: fix bitmap declaration
Date: Thu, 07 Mar 2013 16:06:39 +0000	[thread overview]
Message-ID: <1362672399.2528.32.camel@menhir> (raw)
In-Reply-To: <CAC5umyjw3xzdExvf3TA6i3iH=ortPeJivetUpEyCP5Mzmn6wEg@mail.gmail.com>

Hi,

On Thu, 2013-03-07 at 23:38 +0900, Akinobu Mita wrote:
> 2013/3/7 Steven Whitehouse <swhiteho@redhat.com>:
> > Hi,
> >
> > This doesn't apply over the patch which Dave just sent. Can you redo
> > this against the current GFS2 -nmw tree if it is still required? Thanks,
> 
> I checked Dave's patch.  It fixes the same issue that I was trying to fix.
> So this -v2 patch is not needed anymore.
> 
> But the cleanup patch in v1 ([PATCH 2/2] gfs2: use memchr_inv) is still
> applicable. So I'll resend it soon.

Ok, thanks. I've pushed the memchr_inv patch into the -nmw git tree,

Steve.



  reply	other threads:[~2013-03-07 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 13:29 [Cluster-devel] [PATCH -v2] gfs2: fix bitmap declaration Akinobu Mita
2013-03-06 13:29 ` Akinobu Mita
2013-03-06 15:27 ` [Cluster-devel] " Steven Whitehouse
2013-03-06 15:27   ` Steven Whitehouse
2013-03-07 14:38   ` [Cluster-devel] " Akinobu Mita
2013-03-07 14:38     ` Akinobu Mita
2013-03-07 16:06     ` Steven Whitehouse [this message]
2013-03-07 16:06       ` Steven Whitehouse

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=1362672399.2528.32.camel@menhir \
    --to=swhiteho@redhat.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.