From: Paul Walmsley <paul@pwsan.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 00/10] OMAP: HWMOD fixes and cleanup
Date: Tue, 18 May 2010 12:24:14 -0600 (MDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1005181223380.27473@utopia.booyaka.com> (raw)
In-Reply-To: <1273247055-15165-1-git-send-email-b-cousson@ti.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 272 bytes --]
Hi Benoît,
On Fri, 7 May 2010, Benoit Cousson wrote:
> Here is the serie based on l-o master that prepare the OMAP4 HWMOD database
> introduction.
>
> It was only tested on OMAP4 GP device for the moment using PAB board.
Thanks, queued for 2.6.35.
- Paul
prev parent reply other threads:[~2010-05-18 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 15:44 [PATCH 00/10] OMAP: HWMOD fixes and cleanup Benoit Cousson
2010-05-07 15:44 ` [PATCH 01/10] OMAP4: hwmod: Replace module & device offsets by absolute clkctrl address Benoit Cousson
2010-05-07 15:44 ` [PATCH 02/10] OMAP: CM: Move MAX_MODULE_READY_TIME to cm.h Benoit Cousson
2010-05-07 15:44 ` [PATCH 03/10] OMAP4: hwmod & CM: Implement the omap4_cm_wait_module_ready function Benoit Cousson
2010-05-07 15:44 ` [PATCH 04/10] OMAP4: hwmod: Replace OCPIF_HAS_IDLEST by HWMOD_NO_IDLEST Benoit Cousson
2010-05-26 21:34 ` Kevin Hilman
2010-05-07 15:44 ` [PATCH 05/10] OMAP: hwmod: Fix wrong pointer iteration in oh->slaves Benoit Cousson
2010-05-07 15:44 ` [PATCH 06/10] OMAP: hwmod: Remove IS_ERR check with omap_clk_get_by_name return value Benoit Cousson
2010-05-07 15:44 ` [PATCH 07/10] OMAP: hwmod: Replace WARN by pr_warning if clock lookup failed Benoit Cousson
2010-05-07 15:44 ` [PATCH 08/10] OMAP: hwmod: Do not exit the iteration if one clock init failed Benoit Cousson
2010-05-07 15:44 ` [PATCH 09/10] OMAP: hwmod: Rename hwmod name for the MPU Benoit Cousson
2010-05-07 15:44 ` [PATCH 10/10] OMAP: hwmod: Replace WARN by pr_warning for clockdomain check Benoit Cousson
2010-05-18 18:24 ` Paul Walmsley [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=alpine.DEB.2.00.1005181223380.27473@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.