From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2] Some patches to clean up lock_dlm etc.
Date: Wed, 25 Jun 2008 12:11:09 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0806251209570.27368@trider-g7> (raw)
In-Reply-To: <12143836512525-git-send-email-swhiteho@redhat.com>
On Wed, 25 Jun 2008, swhiteho at redhat.com wrote:
> Hi,
>
> Here are some patches which I've collected up in preparation for
> removal of the lock_dlm module (the plan being to merge it into
> the main GFS2 module). I've not yet made a decision about whether
> they will go into this merge window or the next, and that might
> well depend upon the timing of the final patch in the series which
> actually does the final removal of the module.
In order to have gfs1 available for F10, we need those patches in for
2.6.27 that's what i assume will be the final kernel for F10, otherwise
all the effort becomes mutt till F11.
Fabio
--
I'm going to make him an offer he can't refuse.
next prev parent reply other threads:[~2008-06-25 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 8:47 [Cluster-devel] [GFS2] Some patches to clean up lock_dlm etc swhiteho
2008-06-25 8:47 ` [Cluster-devel] [PATCH] [GFS2] Remove remote lock dropping code swhiteho
2008-06-25 8:47 ` [Cluster-devel] [PATCH] [GFS2] Remove obsolete conversion deadlock avoidance code swhiteho
2008-06-25 8:47 ` [Cluster-devel] [PATCH] [GFS2] Clean up the plock operations swhiteho
2008-06-25 8:47 ` [Cluster-devel] [PATCH] [GFS2] Remove all_list from lock_dlm swhiteho
2008-06-25 10:11 ` Fabio M. Di Nitto [this message]
2008-06-25 10:30 ` [Cluster-devel] [GFS2] Some patches to clean up lock_dlm etc 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=Pine.LNX.4.64.0806251209570.27368@trider-g7 \
--to=fdinitto@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 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).