From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Michael Holzheu <HOLZHEU@de.ibm.com>,
Stefan Weinhuber <wein@de.ibm.com>
Subject: Re: [PATCH] DASD: send 'change' uevents
Date: Sun, 26 Oct 2008 19:29:57 +0100 [thread overview]
Message-ID: <1225045797.14057.15.camel@localhost> (raw)
In-Reply-To: <49016599.5030406@suse.de>
Hi Hannes,
On Fri, 2008-10-24 at 08:05 +0200, Hannes Reinecke wrote:
> this patch modifies the DASD driver to sent out 'change' events
> whenever the internal state machine transitions in or out of the
> 'ready' state. This is required for udev so that vol_id and friends
> can actually read from the disk.
>
> Please apply.
Looks reasonable to me. Stefan can you take a look at this please?
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2008-10-26 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 6:05 [PATCH] DASD: send 'change' uevents Hannes Reinecke
2008-10-26 18:29 ` Martin Schwidefsky [this message]
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=1225045797.14057.15.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=HOLZHEU@de.ibm.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wein@de.ibm.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