From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2/dlm: correct the refmap on recovery master
Date: Thu, 22 Jul 2010 09:58:17 -0700 [thread overview]
Message-ID: <4C4878A9.5060909@oracle.com> (raw)
In-Reply-To: <20100722105131.GB3486@laptop.jp.oracle.com>
On 07/22/2010 03:51 AM, Wengang Wang wrote:
> On 10-07-21 11:19, Sunil Mushran wrote:
>
>> So I discussed this problem with Srini. Yes, your patch is on the right
>> track. Just that it needs to be rebased atop Srini's patch.
>>
>>
> It seems that Srini's patch is not committed to mainline yet.
>
No, it is not as yet. But should be in the queue. Just get the patch from
Srini and rebase your patch atop it.
prev parent reply other threads:[~2010-07-22 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 16:25 [Ocfs2-devel] [PATCH] ocfs2/dlm: correct the refmap on recovery master Wengang Wang
2010-06-25 1:55 ` Wengang Wang
2010-07-05 10:00 ` Wengang Wang
2010-07-19 10:09 ` Wengang Wang
2010-07-19 23:52 ` Sunil Mushran
2010-07-20 2:59 ` Wengang Wang
2010-07-20 22:33 ` Sunil Mushran
2010-07-21 12:22 ` Wengang Wang
2010-07-21 18:19 ` Sunil Mushran
2010-07-22 10:51 ` Wengang Wang
2010-07-22 16:58 ` Sunil Mushran [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=4C4878A9.5060909@oracle.com \
--to=sunil.mushran@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).