From: Lars Roland <lroland@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: David Teigland <teigland@redhat.com>,
linux-kernel@vger.kernel.org, linux-cluster@redhat.com
Subject: Re: [PATCH 0/8] dlm: overview
Date: Tue, 17 May 2005 15:26:09 +0200 [thread overview]
Message-ID: <4ad99e0505051706265ea06f7@mail.gmail.com> (raw)
In-Reply-To: <20050517001133.64d50d8c.akpm@osdl.org>
On 5/17/05, Andrew Morton <akpm@osdl.org> wrote:
> The usual fallback is to identify all the stakeholders and get them to say
> "yes Andrew, this code is cool and we can use it", but I don't think the
> clustering teams have sufficent act-togetherness to be able to do that.
It is highly unlikely that this will ever happen because of the
different nature of these projects. That said getting a kernel system
for dlm and message passing should be doable given the wide variety
off uses they have.
next prev parent reply other threads:[~2005-05-17 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 7:19 [PATCH 0/8] dlm: overview David Teigland
2005-05-17 7:11 ` Andrew Morton
2005-05-17 9:57 ` David Teigland
2005-05-17 13:10 ` Andi Kleen
2005-05-17 13:26 ` Lars Roland [this message]
2005-05-17 17:07 ` Daniel Phillips
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=4ad99e0505051706265ea06f7@mail.gmail.com \
--to=lroland@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-cluster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=teigland@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