From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: RHEL5 - gfs-kernel: Bug 450209: Create gfs1-specific lock modules.
Date: Mon, 04 Aug 2008 10:01:59 -0500 [thread overview]
Message-ID: <489719E7.3010001@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0808040924400.14806@trider-g7>
Fabio M. Di Nitto wrote:
> On Thu, 31 Jul 2008, Abhijith Das wrote:
>
>
>> Gitweb: http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=5a201a3c8c0fde6289514e43faf0ae6e4456db8c
>> Commit: 5a201a3c8c0fde6289514e43faf0ae6e4456db8c
>> Parent: aee3ab578619a22e03cc9c9d024647927df479b0
>> Author: Abhijith Das <adas@redhat.com>
>> AuthorDate: Thu Jul 31 16:00:07 2008 -0500
>> Committer: Abhijith Das <adas@redhat.com>
>> CommitterDate: Thu Jul 31 16:11:17 2008 -0500
>>
>> gfs-kernel: Bug 450209: Create gfs1-specific lock modules.
>>
>> Pulled lock_dlm and lock_nolock files from the kernel and included in gfs. gfs is no longer dependent on gfs2.ko, lock_dlm.ko or lock_nolock.ko
>>
>
> Hi Abhi,
>
> any idea when this patch can hit master? A cherry pick applies fine but
> then it doesn't build and I don't want to step on your toes if you are
> already working on it.
>
Fabio,
The patch for upstream is slightly different and I'm working on it
today. I should have something for you tonight.
Cheers!
--Abhi
> Thanks
> Fabio
>
> --
> I'm going to make him an offer he can't refuse.
>
>
prev parent reply other threads:[~2008-08-04 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080731211420.35A34A823D@lists.fedorahosted.org>
2008-08-04 7:26 ` [Cluster-devel] Re: RHEL5 - gfs-kernel: Bug 450209: Create gfs1-specific lock modules Fabio M. Di Nitto
2008-08-04 15:01 ` Abhijith Das [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=489719E7.3010001@redhat.com \
--to=adas@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).