From: Alasdair G Kergon <agk@redhat.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: device-mapper development <dm-devel@redhat.com>,
Peter Rajnoha <prajnoha@redhat.com>
Subject: Re: [PATCH 1/3] Send KOBJ_ADD event after dm resume ioctl.
Date: Fri, 19 Mar 2010 13:47:58 +0000 [thread overview]
Message-ID: <20100319134758.GD919@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <ac3eb2511003190643u32a8e702l4e7774e7ec924a12@mail.gmail.com>
On Fri, Mar 19, 2010 at 02:43:13PM +0100, Kay Sievers wrote:
> Sure, but as mentioned earlier, these events are just expected to
> fail, and update the current udev state, if they can't retrieve the
> needed information or find out that the device in not usable.
They have to 'fail' in a controlled way that does not interfere
with any other processing that may already be happening.
Alasdair
next prev parent reply other threads:[~2010-03-19 13:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 13:58 [PATCH 1/3] Send KOBJ_ADD event after dm resume ioctl Milan Broz
2010-03-18 13:58 ` [PATCH 2/3] Add genhd flag requesting notification of partition changes only Milan Broz
2010-03-18 13:58 ` [PATCH 3/3] Do not send multiple REMOVE events for kobjects Milan Broz
2010-03-18 16:13 ` [PATCH 1/3] Send KOBJ_ADD event after dm resume ioctl Kay Sievers
2010-03-18 17:24 ` Alasdair G Kergon
2010-03-18 21:35 ` Milan Broz
2010-03-19 8:27 ` Kay Sievers
2010-03-19 9:06 ` Lars Ellenberg
2010-03-19 9:24 ` Kay Sievers
2010-03-19 9:49 ` Milan Broz
2010-03-19 10:16 ` Kay Sievers
2010-03-19 11:14 ` Milan Broz
2010-03-19 11:44 ` Kay Sievers
2010-03-19 12:08 ` Milan Broz
2010-03-19 12:14 ` Kay Sievers
2010-03-19 11:50 ` Hannes Reinecke
2010-03-19 12:00 ` Alasdair G Kergon
2010-03-19 12:12 ` Alasdair G Kergon
2010-03-19 12:16 ` Kay Sievers
2010-03-19 13:17 ` Peter Rajnoha
2010-03-19 13:24 ` Peter Rajnoha
2010-03-19 13:43 ` Kay Sievers
2010-03-19 13:47 ` Alasdair G Kergon [this message]
2010-03-19 13:58 ` David Zeuthen
2010-03-19 14:34 ` Alasdair G Kergon
2010-03-19 14:59 ` David Zeuthen
2010-03-19 15:24 ` Alasdair G Kergon
2010-03-19 16:01 ` David Zeuthen
2010-03-19 16:36 ` Alasdair G Kergon
2010-03-22 10:11 ` Milan Broz
2010-03-19 15:55 ` Mike Snitzer
2010-03-19 16:08 ` David Zeuthen
2010-03-19 14:08 ` Hannes Reinecke
2010-03-19 15:05 ` Peter Rajnoha
2010-03-19 15:14 ` David Zeuthen
2010-03-19 15:51 ` Peter Rajnoha
2010-03-19 9:10 ` Milan Broz
2010-03-19 9:22 ` Kay Sievers
2010-03-19 9:42 ` Hannes Reinecke
2010-03-19 12:27 ` 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=20100319134758.GD919@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=prajnoha@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 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.