From: David Brownell <david-b@pacbell.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Andrew Victor <andrew@sanpeople.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-pm@lists.linux-foundation.org
Subject: Re: [patch 2.6.23-rc2 1/2] define clk_must_disable()
Date: Tue, 7 Aug 2007 13:18:37 -0700 [thread overview]
Message-ID: <200708071318.37585.david-b@pacbell.net> (raw)
In-Reply-To: <20070807125054.GC2833@flint.arm.linux.org.uk>
On Tuesday 07 August 2007, Russell King wrote:
> 2. it's unclear how this function obtains information about the "upcoming
> system state" and therefore decides whether the particular clock may
> be available.
Why should any such *implementation detail* matter to an interface spec?
Especially to the clock framework, which has already gone to great
lengths to avoid constraining implementations, and allow them to do
whatever the platform needs. (Admittedly, some people don't think
of that as a feature.)
- Dave
next prev parent reply other threads:[~2007-08-07 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 18:11 [patch 2.6.23-rc2 1/2] define clk_must_disable() David Brownell
2007-08-06 20:04 ` Russell King
2007-08-06 20:38 ` David Brownell
2007-08-06 21:03 ` David Brownell
2007-08-06 21:48 ` Russell King
2007-08-06 23:46 ` David Brownell
2007-08-07 5:23 ` Andrew Morton
2007-08-07 12:50 ` Russell King
2007-08-07 17:21 ` Andrew Morton
2007-08-07 17:25 ` Russell King
2007-08-07 20:15 ` David Brownell
2007-08-07 20:18 ` David Brownell [this message]
2007-08-07 21:04 ` David Brownell
2007-08-07 21:17 ` David Brownell
2007-08-07 22:20 ` Rafael J. Wysocki
2007-08-07 21:20 ` David Brownell
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=200708071318.37585.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=andrew@sanpeople.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rmk@arm.linux.org.uk \
/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