public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Premi, Sanjeev" <premi@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC] AM35x: Workaround to use generic OMAP3 hwmods
Date: Fri, 4 Mar 2011 10:23:06 +0100	[thread overview]
Message-ID: <4D70AF7A.90009@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103031652500.10981@utopia.booyaka.com>

Hi Paul,

On 3/4/2011 12:53 AM, Paul Walmsley wrote:
> On Thu, 3 Mar 2011, Paul Walmsley wrote:
>
>> On Fri, 25 Feb 2011, Cousson, Benoit wrote:
>>
>>>   static struct omap_hwmod_ocp_if *omap3xxx_l4_core_slaves[] = {
>>>   	&omap3xxx_l3_main__l4_core,
>>> -	&omap3_l4_core__sr1,
>>> -	&omap3_l4_core__sr2,
>
> Never mind, I see the issue now...

It was simply wrong as explained in the answer to Sanjeev.
I do agree that the changelog does not say anything about it, sorry 
about that.

BTW, do you want me to re-send that patch properly and not hidden in 
previous email thread with Sanjeev?

Thanks
Benoit

  reply	other threads:[~2011-03-04  9:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 13:48 [RFC] AM35x: Workaround to use generic OMAP3 hwmods Sanjeev Premi
2011-02-25 17:02 ` Cousson, Benoit
2011-03-03 23:15   ` Paul Walmsley
2011-03-03 23:53     ` Paul Walmsley
2011-03-04  9:23       ` Cousson, Benoit [this message]
2011-03-04 18:41         ` Paul Walmsley
2011-03-10  2:37   ` Paul Walmsley
2011-03-10  8:39     ` Cousson, Benoit
2011-03-10 10:23       ` Cousson, Benoit
2011-03-10 11:09         ` Paul Walmsley
2011-03-11  8:33     ` Premi, Sanjeev

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=4D70AF7A.90009@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=premi@ti.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