From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Power parents
Date: Fri, 08 Oct 2004 08:59:05 +1000 [thread overview]
Message-ID: <1097189945.16223.8.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0410071444220.650-100000@ida.rowland.org>
On Fri, 2004-10-08 at 04:46, Alan Stern wrote:
> Ben:
>
> Pavel Machek suggested you were a good person to ask this question.
>
> I see that the power tree agrees pretty much with the device tree, but
> there is the possibility of having a different parent pointer. However
> the device_pm_set_parent() routine isn't called anywhere in the kernel.
> Does that mean it can be eliminated, making the two trees identical?
Currently the trees are identical yes. I may still want to "insert"
special nodes in the Power tree though...
Ben.
next prev parent reply other threads:[~2004-10-07 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 18:46 Power parents Alan Stern
2004-10-07 22:59 ` Benjamin Herrenschmidt [this message]
2004-10-08 14:07 ` Alan Stern
2004-10-09 1:12 ` Benjamin Herrenschmidt
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=1097189945.16223.8.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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