From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH 1/2] dlm: Send lockspace name with uevents
Date: Tue, 13 Oct 2009 10:23:30 -0500 [thread overview]
Message-ID: <20091013152330.GC27036@redhat.com> (raw)
In-Reply-To: <20091013145337.GA27036@redhat.com>
On Tue, Oct 13, 2009 at 09:53:37AM -0500, David Teigland wrote:
> On Tue, Oct 13, 2009 at 03:56:15PM +0100, Steven Whitehouse wrote:
> > Although it is possible to get this information from the path,
> > its much easier to provide the lockspace as a seperate env
> > variable.
>
> I don't mind this, but it's more or less a style issue. I'm going to try to
> keep upstream and rhel as close as possible for a while to minimize the
> backporting work in the early stages when it's usually heaviest. That means
> putting off things like this until later.
Also, libudev may make this less relevant,
http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/
Dave
next prev parent reply other threads:[~2009-10-13 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 14:56 [Cluster-devel] A couple of DLM patches Steven Whitehouse
2009-10-13 14:56 ` [Cluster-devel] [PATCH 1/2] dlm: Send lockspace name with uevents Steven Whitehouse
2009-10-13 14:53 ` [Cluster-devel] " David Teigland
2009-10-13 15:23 ` David Teigland [this message]
2009-10-13 15:43 ` Steven Whitehouse
2009-10-13 14:56 ` [Cluster-devel] [PATCH 2/2] dlm: Add down/up_write_non_owner to keep lockdep happy Steven Whitehouse
2009-11-12 13:27 ` [Cluster-devel] " Steven Whitehouse
[not found] ` <20091112142211.GA468@elte.hu>
2009-11-12 14:29 ` Steven Whitehouse
2009-11-12 17:14 ` David Teigland
2009-11-12 17:24 ` Steven Whitehouse
2009-11-12 18:34 ` David Teigland
2009-11-13 10:21 ` Steven Whitehouse
[not found] ` <1258044339.4039.685.camel@laptop>
2009-11-12 17:27 ` Steven Whitehouse
2009-11-12 18:21 ` David Teigland
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=20091013152330.GC27036@redhat.com \
--to=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;
as well as URLs for NNTP newsgroup(s).