From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: Re: Possible problem with device_move()
Date: Wed, 1 Aug 2007 15:03:32 +0200 [thread overview]
Message-ID: <20070801150332.41f447c8@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0707311628150.2787-100000@iolanthe.rowland.org>
On Tue, 31 Jul 2007 16:37:03 -0400 (EDT),
Alan Stern <stern@rowland.harvard.edu> wrote:
> Still, I suppose it would be best to add a "move device A to the end of
> the dpm_active list" routine for use in this sort of situation. This
> should be easy to do.
Would it make sense if device_move() moved the new parent (and its
parents) after the device in the dpm_active list automatically? Then we
would only have to worry about reordering manually in very special
cases.
next prev parent reply other threads:[~2007-08-01 13:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 15:36 Possible problem with device_move() Alan Stern
2007-07-30 6:42 ` Cornelia Huck
2007-07-30 17:34 ` Alan Stern
2007-07-31 8:33 ` Cornelia Huck
2007-07-31 15:11 ` Alan Stern
2007-07-31 15:27 ` Rafael J. Wysocki
2007-07-31 15:30 ` Cornelia Huck
2007-07-31 18:17 ` Alan Stern
2007-07-31 19:12 ` Rafael J. Wysocki
2007-07-31 20:37 ` Alan Stern
2007-08-01 13:03 ` Cornelia Huck [this message]
2007-08-01 15:22 ` Alan Stern
2007-08-01 17:04 ` Cornelia Huck
2007-08-01 17:35 ` Alan Stern
2007-08-01 19:25 ` Rafael J. Wysocki
2007-08-01 20:27 ` Alan Stern
2007-08-02 8:06 ` Cornelia Huck
2007-08-02 14:19 ` Alan Stern
2007-08-02 14:50 ` Cornelia Huck
2007-08-02 11:21 ` Rafael J. Wysocki
2007-08-02 14:24 ` Alan Stern
2007-08-02 14:58 ` Rafael J. Wysocki
2007-08-02 15:23 ` Alan Stern
2007-08-02 22:39 ` Rafael J. Wysocki
2007-08-03 14:56 ` Alan Stern
2007-08-03 21:39 ` Rafael J. Wysocki
2007-08-06 9:31 ` Cornelia Huck
2007-08-06 13:53 ` Alan Stern
2007-07-30 6:53 ` Marcel Holtmann
2007-07-30 17:37 ` Alan Stern
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=20070801150332.41f447c8@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=marcel@holtmann.org \
--cc=stern@rowland.harvard.edu \
/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