From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
hvaibhav@ti.com
Subject: Re: [GIT PULL] ARM: OMAP AM33xx: clock data for 3.6
Date: Thu, 5 Jul 2012 01:11:34 -0700 [thread overview]
Message-ID: <20120705081134.GS1122@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207040323500.6760@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [120704 02:29]:
> Hi Tony
>
> The following changes since commit 6fd8246b1c1167c983b089f9eaafa13ef9ca7adf:
>
> Merge tag 'omap-devel-a-for-3.6' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into devel-am33xx (2012-06-22 01:50:22 -0700)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-devel-e-for-3.5
>
> for you to fetch changes up to e30384abd63dfa11508a38243e1d78f1d70486b1:
>
> ARM: OMAP3+: clock33xx: Add AM33XX clock tree data (2012-06-29 16:16:40 -0600)
>
> ----------------------------------------------------------------
> OMAP AM33xx clock data
>
> ----------------------------------------------------------------
Thanks pulled into devel-am33xx-part2 and fixed up cpu_is_am33xx to
use soc_is_am33xx.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP AM33xx: clock data for 3.6
Date: Thu, 5 Jul 2012 01:11:34 -0700 [thread overview]
Message-ID: <20120705081134.GS1122@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207040323500.6760@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [120704 02:29]:
> Hi Tony
>
> The following changes since commit 6fd8246b1c1167c983b089f9eaafa13ef9ca7adf:
>
> Merge tag 'omap-devel-a-for-3.6' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into devel-am33xx (2012-06-22 01:50:22 -0700)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-devel-e-for-3.5
>
> for you to fetch changes up to e30384abd63dfa11508a38243e1d78f1d70486b1:
>
> ARM: OMAP3+: clock33xx: Add AM33XX clock tree data (2012-06-29 16:16:40 -0600)
>
> ----------------------------------------------------------------
> OMAP AM33xx clock data
>
> ----------------------------------------------------------------
Thanks pulled into devel-am33xx-part2 and fixed up cpu_is_am33xx to
use soc_is_am33xx.
Tony
next prev parent reply other threads:[~2012-07-05 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 9:25 [GIT PULL] ARM: OMAP AM33xx: clock data for 3.6 Paul Walmsley
2012-07-04 9:25 ` Paul Walmsley
2012-07-05 8:11 ` Tony Lindgren [this message]
2012-07-05 8:11 ` 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=20120705081134.GS1122@atomide.com \
--to=tony@atomide.com \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.