All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/3] ocfs2/dlm: dlm_is_lockres_migrateable() returns boolean
Date: Mon, 23 May 2011 23:53:40 -0700	[thread overview]
Message-ID: <20110524065340.GA24290@noexit.corp.google.com> (raw)
In-Reply-To: <4DC32186.7000200@oracle.com>

On Thu, May 05, 2011 at 03:15:34PM -0700, Sunil Mushran wrote:
> ok.

I don't have your original email to reply to, but I got it off of your
patch directory.  It's now in the merge-window branch of ocfs2.git.

Joel

-- 

"When I am working on a problem I never think about beauty. I
 only think about how to solve the problem. But when I have finished, if
 the solution is not beautiful, I know it is wrong."
         - Buckminster Fuller

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

      reply	other threads:[~2011-05-24  6:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 23:03 [Ocfs2-devel] [PATCH 1/3] ocfs2/dlm: dlm_is_lockres_migrateable() returns boolean Sunil Mushran
2011-04-26 23:03 ` [Ocfs2-devel] [PATCH 2/3] ocfs2/dlm: Add new dlm message DLM_BEGIN_EXIT_DOMAIN_MSG Sunil Mushran
2011-05-05 22:12   ` Mark Fasheh
2011-04-26 23:03 ` [Ocfs2-devel] [PATCH 3/3] ocfs2/dlm: Do not migrate resource to a node that is leaving the domain Sunil Mushran
2011-05-05 22:24   ` Mark Fasheh
2011-05-05 22:44     ` Sunil Mushran
2011-05-05 23:28       ` Mark Fasheh
2011-05-05 23:44         ` Sunil Mushran
2011-05-10  6:19   ` Wengang Wang
2011-05-10 17:17     ` Sunil Mushran
2011-05-05 22:09 ` [Ocfs2-devel] [PATCH 1/3] ocfs2/dlm: dlm_is_lockres_migrateable() returns boolean Mark Fasheh
2011-05-05 22:15   ` Sunil Mushran
2011-05-24  6:53     ` Joel Becker [this message]

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=20110524065340.GA24290@noexit.corp.google.com \
    --to=jlbec@evilplan.org \
    --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.