From: Nishanth Menon <nm@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: Koen Kooi <koen@beagleboard.org>,
"Hilman, Kevin" <khilman@ti.com>,
l-o <linux-omap@vger.kernel.org>,
l-a <linux-arm-kernel@lists.infradead.org>,
Tony <tony@atomide.com>
Subject: Re: [PATCH 2/2] OMAP3: beagle xm: enable upto 800MHz OPP
Date: Thu, 06 Jan 2011 08:00:56 -0600 [thread overview]
Message-ID: <4D25CB18.3080904@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930248201A37@dbde02.ent.ti.com>
Premi, Sanjeev had written, on 01/06/2011 07:58 AM, the following:
[..]
> Some of the patches generic that Koen attached are based on my
> submissions. As part of migration to 2.6.37, I am in process of
> validating them on internal integration tree. Will post them
> soon... may be end of tomorrow.
>
> I will be testing them on OMAP3EVM.
Sure. please do post them to l-o and cc l-a - I suppose until then, they
are unofficial if they are lying around in some private tree(even if
viewable over internet ;) ).
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] OMAP3: beagle xm: enable upto 800MHz OPP
Date: Thu, 06 Jan 2011 08:00:56 -0600 [thread overview]
Message-ID: <4D25CB18.3080904@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930248201A37@dbde02.ent.ti.com>
Premi, Sanjeev had written, on 01/06/2011 07:58 AM, the following:
[..]
> Some of the patches generic that Koen attached are based on my
> submissions. As part of migration to 2.6.37, I am in process of
> validating them on internal integration tree. Will post them
> soon... may be end of tomorrow.
>
> I will be testing them on OMAP3EVM.
Sure. please do post them to l-o and cc l-a - I suppose until then, they
are unofficial if they are lying around in some private tree(even if
viewable over internet ;) ).
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2011-01-06 14:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 20:49 [PATCH 0/2] OMAP3: Beagle: enable 800MHz for xm Nishanth Menon
2011-01-05 20:49 ` Nishanth Menon
2011-01-05 20:49 ` [PATCH 1/2] omap3|4: opp: make omapx_opp_init non-static Nishanth Menon
2011-01-05 20:49 ` Nishanth Menon
2011-02-01 22:01 ` Kevin Hilman
2011-02-01 22:01 ` Kevin Hilman
2011-01-05 20:49 ` [PATCH 2/2] OMAP3: beagle xm: enable upto 800MHz OPP Nishanth Menon
2011-01-05 20:49 ` Nishanth Menon
2011-01-05 23:28 ` Kevin Hilman
2011-01-05 23:28 ` Kevin Hilman
2011-01-06 12:24 ` Nishanth Menon
2011-01-06 12:24 ` Nishanth Menon
2011-01-06 13:00 ` Koen Kooi
2011-01-06 13:00 ` Koen Kooi
2011-01-06 13:44 ` Nishanth Menon
2011-01-06 13:44 ` Nishanth Menon
2011-01-06 13:58 ` Premi, Sanjeev
2011-01-06 13:58 ` Premi, Sanjeev
2011-01-06 14:00 ` Nishanth Menon [this message]
2011-01-06 14:00 ` Nishanth Menon
2011-01-06 14:22 ` Premi, Sanjeev
2011-01-06 14:22 ` Premi, Sanjeev
2011-01-06 14:01 ` Koen Kooi
2011-01-06 14:01 ` Koen Kooi
2011-01-06 14:07 ` Nishanth Menon
2011-01-06 14:07 ` Nishanth Menon
2011-01-07 13:04 ` Aaro Koskinen
2011-01-07 13:04 ` Aaro Koskinen
2011-01-07 13:30 ` Nishanth Menon
2011-01-07 13:30 ` Nishanth Menon
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=4D25CB18.3080904@ti.com \
--to=nm@ti.com \
--cc=khilman@ti.com \
--cc=koen@beagleboard.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.com \
--cc=tony@atomide.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 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.