From: Dirk Behme <dirk.behme@de.bosch.com>
To: linux-omap-open-source@linux.omap.com
Subject: Re: Some comments on Linux-OMAP tree by Russell King
Date: Wed, 14 Dec 2005 20:37:00 +0100 [thread overview]
Message-ID: <43A0745C.7090005@de.bosch.com> (raw)
Romain Goyet wrote:
> By the way, Russell also added this :
>
>>Hmm, I notice that omap folk are _still_ buggering up the MMC core in
>>relation to mmc.c. It'd also be nice of omap folk could conform to
>>the agreed usage of clk_use/unuse vs clk_enable/disable as documented
>>in the header file. The clock framework *relies* on everyone
>>following the rules. Frustrated sigh.
Everybody who is interested in this, "Clock framework" thread on
linux-arm-kernel starting with (still ongoing)
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-December/032851.html
Dirk
next reply other threads:[~2005-12-14 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 19:37 Dirk Behme [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-14 14:25 Some comments on Linux-OMAP tree by Russell King Romain Goyet
2005-12-30 22:17 ` Tony Lindgren
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=43A0745C.7090005@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=linux-omap-open-source@linux.omap.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