From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 4/6] ocfs2/dlm: Move struct dlm_master_list_entry to dlmcommon.h
Date: Tue Mar 4 13:57:26 2008 [thread overview]
Message-ID: <47CDC5BF.5050005@oracle.com> (raw)
In-Reply-To: <20080304215436.GN9349@ca-server1.us.oracle.com>
ok. I'll push #4 with the next series.
Mark Fasheh wrote:
> On Mon, Mar 03, 2008 at 10:36:14AM -0800, Sunil Mushran wrote:
>
>> Was trying to balance out the number of patches in both. :)
>> I mean I wanted this cleanup irrespective of the debugfs series.
>>
>
> I applied these patches sans #4 and things seemed ok. Should the end result
> be acceptable? I think everything except this patch looks like 2.6.25
> material...
> --Mark
>
> --
> Mark Fasheh
> Principal Software Developer, Oracle
> mark.fasheh@oracle.com
>
next prev parent reply other threads:[~2008-03-04 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 14:04 [Ocfs2-devel] DLM bug fixes and cleanups Sunil Mushran
2008-03-01 14:04 ` [Ocfs2-devel] [PATCH 6/6] ocfs2/dlm: dlm_thread should not sleep while holding the dlm_spinlock Sunil Mushran
2008-03-02 18:52 ` Joel Becker
2008-03-01 14:04 ` [Ocfs2-devel] [PATCH 1/6] ocfs2/dlm: Add missing dlm_lock_put()s Sunil Mushran
2008-03-02 18:12 ` Joel Becker
2008-03-01 14:04 ` [Ocfs2-devel] [PATCH 4/6] ocfs2/dlm: Move struct dlm_master_list_entry to dlmcommon.h Sunil Mushran
2008-03-02 18:18 ` Joel Becker
2008-03-03 10:36 ` Sunil Mushran
2008-03-03 12:28 ` Joel Becker
2008-03-04 13:55 ` Mark Fasheh
2008-03-04 13:57 ` Sunil Mushran [this message]
2008-03-01 14:04 ` [Ocfs2-devel] [PATCH 5/6] ocfs2/dlm: Print message showing the recovery master Sunil Mushran
2008-03-01 14:04 ` [Ocfs2-devel] [PATCH 3/6] ocfs2/dlm: Add missing dlm_lockres_put()s Sunil Mushran
2008-03-02 18:16 ` Joel Becker
2008-03-01 14:04 ` [Ocfs2-devel] [PATCH 2/6] ocfs2/dlm: Add missing dlm_lockres_put()s in migration path Sunil Mushran
2008-03-02 18:14 ` 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=47CDC5BF.5050005@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 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.