From: Kay Sievers <kay.sievers@vrfy.org>
To: Mike Anderson <andmike@us.ibm.com>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org,
Greg KH <greg@kroah.com>
Subject: Re: [RFC 0/3] dm: add path uevents
Date: Wed, 15 Aug 2007 00:58:34 +0200 [thread overview]
Message-ID: <1187132314.4312.47.camel@lov.localdomain> (raw)
In-Reply-To: <20070814200544.963756967@us.ibm.com>>
On Tue, 2007-08-14 at 13:05 -0700, Mike Anderson wrote:
> This patch series enables device mapper (dm) to send kobject uevents for
> dm events. Currently only two new events are sent related to path state
> changes.
Sounds fine.
> DM_ACTION=PATH_FAILED
> DM_SEQNUM=1
> DM_PATH=8:48
> DM_PATHS=1
Oh, I have a patch pending for dmsetup to export a bunch of variables in
the environment format with a single call, so we can use it udev
context.
Here is the list, just that we don't clash with names or use the same
names where appropriate:
DM_NAME=
DM_UUID=
DM_STATE=
DM_TABLE_STATE=
DM_OPENCOUNT=
DM_MAJOR=
DM_MINOR=
DM_TARGET_COUNT=
DM_TARGET_TYPES=
DM_LAST_EVENT_NR=
Let me know if something should be renamed.
Thanks,
Kay
parent reply other threads:[~2007-08-14 22:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070814200544.963756967@us.ibm.com>]
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=1187132314.4312.47.camel@lov.localdomain \
--to=kay.sievers@vrfy.org \
--cc=andmike@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®