From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [Kernel PATCH] emit change on devmapper devices
Date: Mon, 12 Nov 2007 16:20:52 -0500 [thread overview]
Message-ID: <4738C3B4.8020504@cfl.rr.com> (raw)
In-Reply-To: <1194454207.6273.5.camel@wing-commander>
Scott James Remnant wrote:
> Hi guys,
>
> I've had this patch sitting on my disk for a few months, and haven't
> done anything more than test it. Before I stuff it into git, and send
> it to the kernel, would you guys have a look over it and see whether
> it's technically correct.
>
> The patch simply causes a kobject "change" event to be emitted on
> devmapper block devices when they are renamed.
When they are renamed? Don't you want a change event when you modify
the table?
WARNING: multiple messages have this Message-ID (diff)
From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [dm-devel] [Kernel PATCH] emit change on devmapper devices
Date: Mon, 12 Nov 2007 21:20:52 +0000 [thread overview]
Message-ID: <4738C3B4.8020504@cfl.rr.com> (raw)
In-Reply-To: <1194454207.6273.5.camel@wing-commander>
Scott James Remnant wrote:
> Hi guys,
>
> I've had this patch sitting on my disk for a few months, and haven't
> done anything more than test it. Before I stuff it into git, and send
> it to the kernel, would you guys have a look over it and see whether
> it's technically correct.
>
> The patch simply causes a kobject "change" event to be emitted on
> devmapper block devices when they are renamed.
When they are renamed? Don't you want a change event when you modify
the table?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-11-12 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 16:50 [Kernel PATCH] emit change on devmapper devices Scott James Remnant
2007-11-07 16:50 ` Scott James Remnant
2007-11-07 17:18 ` Linas Vepstas
2007-11-07 17:18 ` Linas Vepstas
2007-11-12 21:20 ` Phillip Susi [this message]
2007-11-12 21:20 ` [dm-devel] " Phillip Susi
2007-11-12 21:34 ` Alasdair G Kergon
2007-11-12 21:34 ` [dm-devel] " Alasdair G Kergon
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=4738C3B4.8020504@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=dm-devel@redhat.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.