From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
b-cousson@ti.com, keshava_mgowda@ti.com
Subject: Re: [GIT PULL v3] ARM: OMAP: Cortex-A9 PERIPHCLK node for 3.2
Date: Tue, 8 Nov 2011 08:56:18 -0800 [thread overview]
Message-ID: <20111108165618.GK31337@atomide.com> (raw)
In-Reply-To: <CAMQu2gwAezM7WZRyZFijYf0vLGEWRaUOGkyctBp=9A5+7oV=tA@mail.gmail.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [111107 23:33]:
> On Tue, Nov 8, 2011 at 1:23 PM, Paul Walmsley <paul@pwsan.com> wrote:
> > On Fri, 4 Nov 2011, Tony Lindgren wrote:
> >
> >> * Paul Walmsley <paul@pwsan.com> [111010 17:09]:
> >> > The following changes since commit be73246058737beec52ae232bcab7776332a9e06:
> >> >
> >> > ARM: OMAP2+: Remove custom init_irq for remaining boards (2011-09-26 17:50:37 -0700)
> >> >
> >> > are available in the git repository at:
> >> > git://git.pwsan.com/linux-2.6 clock_hwmod_devel_3.2
> >> >
> >> > This pull request drops the EHCI/OHCI hwmod data due to some
> >> > inconsistencies that were just found in the data.
> >> >
> >> > Santosh Shilimkar (1):
> >> > ARM: OMAP4: clock: Add CPU local timer clock node.
> >> >
> >> > arch/arm/mach-omap2/clock44xx_data.c | 9 +++++++++
> >> > 1 files changed, 9 insertions(+), 0 deletions(-)
> >>
> >> Should this be pulled into fixes for v3.2 -rc cycle?
> >
> > Santosh would be the right person to ask. Santosh, is anything broken in
> > 3.2 if this patch doesn't get merged in -rc? Or is it just a feature
> > which could be added in 3.3?
> >
> Nope nothing broken now since OMAP CPUFreq has not
> got into mainline yet. We need this patch to present once we
> start supporting MPU frequency scaling which I guess would
> happen now in 3.3.
OK thanks for the update.
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v3] ARM: OMAP: Cortex-A9 PERIPHCLK node for 3.2
Date: Tue, 8 Nov 2011 08:56:18 -0800 [thread overview]
Message-ID: <20111108165618.GK31337@atomide.com> (raw)
In-Reply-To: <CAMQu2gwAezM7WZRyZFijYf0vLGEWRaUOGkyctBp=9A5+7oV=tA@mail.gmail.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [111107 23:33]:
> On Tue, Nov 8, 2011 at 1:23 PM, Paul Walmsley <paul@pwsan.com> wrote:
> > On Fri, 4 Nov 2011, Tony Lindgren wrote:
> >
> >> * Paul Walmsley <paul@pwsan.com> [111010 17:09]:
> >> > The following changes since commit be73246058737beec52ae232bcab7776332a9e06:
> >> >
> >> > ? ARM: OMAP2+: Remove custom init_irq for remaining boards (2011-09-26 17:50:37 -0700)
> >> >
> >> > are available in the git repository at:
> >> > ? git://git.pwsan.com/linux-2.6 clock_hwmod_devel_3.2
> >> >
> >> > This pull request drops the EHCI/OHCI hwmod data due to some
> >> > inconsistencies that were just found in the data.
> >> >
> >> > Santosh Shilimkar (1):
> >> > ? ? ? ARM: OMAP4: clock: Add CPU local timer clock node.
> >> >
> >> > ?arch/arm/mach-omap2/clock44xx_data.c | ? ?9 +++++++++
> >> > ?1 files changed, 9 insertions(+), 0 deletions(-)
> >>
> >> Should this be pulled into fixes for v3.2 -rc cycle?
> >
> > Santosh would be the right person to ask. ?Santosh, is anything broken in
> > 3.2 if this patch doesn't get merged in -rc? ?Or is it just a feature
> > which could be added in 3.3?
> >
> Nope nothing broken now since OMAP CPUFreq has not
> got into mainline yet. We need this patch to present once we
> start supporting MPU frequency scaling which I guess would
> happen now in 3.3.
OK thanks for the update.
Tony
next prev parent reply other threads:[~2011-11-08 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 19:44 [GIT PULL] ARM: OMAP: new miscellaneous clock/hwmod data for 3.2 Paul Walmsley
2011-10-10 19:44 ` Paul Walmsley
2011-10-10 20:16 ` [GIT PULL v2] " Paul Walmsley
2011-10-11 0:43 ` [GIT PULL v3] ARM: OMAP: Cortex-A9 PERIPHCLK node " Paul Walmsley
2011-11-05 0:53 ` Tony Lindgren
2011-11-05 0:53 ` Tony Lindgren
2011-11-08 7:53 ` Paul Walmsley
2011-11-08 7:53 ` Paul Walmsley
2011-11-08 8:07 ` Shilimkar, Santosh
2011-11-08 8:07 ` Shilimkar, Santosh
2011-11-08 16:56 ` Tony Lindgren [this message]
2011-11-08 16:56 ` 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=20111108165618.GK31337@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@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 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.