From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/2] omap soc changes for v3.19
Date: Thu, 20 Nov 2014 11:43:08 +0100 [thread overview]
Message-ID: <201411201143.08649.arnd@arndb.de> (raw)
In-Reply-To: <pull-1415999057-591605>
On Friday 14 November 2014, Tony Lindgren wrote:
> The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:
>
> Linux 3.18-rc2 (2014-10-26 16:48:41 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.19/clocks-and-pm
>
> for you to fetch changes up to 9889278181bcdbae882664d8cee5bb0e064397e4:
>
> Merge tag 'for-v3.19/omap-a' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.19/soc (2014-11-14 10:25:12 -0800)
>
> ----------------------------------------------------------------
> SoC related changes for omaps. Mostly to make PM easier to use for
> omap4 and later, and to fix clock DPLL fixes by adding determine_rate
> and set_rate_and_parent.
>
pulled into next/soc, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] omap soc changes for v3.19
Date: Thu, 20 Nov 2014 11:43:08 +0100 [thread overview]
Message-ID: <201411201143.08649.arnd@arndb.de> (raw)
In-Reply-To: <pull-1415999057-591605>
On Friday 14 November 2014, Tony Lindgren wrote:
> The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:
>
> Linux 3.18-rc2 (2014-10-26 16:48:41 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.19/clocks-and-pm
>
> for you to fetch changes up to 9889278181bcdbae882664d8cee5bb0e064397e4:
>
> Merge tag 'for-v3.19/omap-a' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.19/soc (2014-11-14 10:25:12 -0800)
>
> ----------------------------------------------------------------
> SoC related changes for omaps. Mostly to make PM easier to use for
> omap4 and later, and to fix clock DPLL fixes by adding determine_rate
> and set_rate_and_parent.
>
pulled into next/soc, thanks!
Arnd
next prev parent reply other threads:[~2014-11-20 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 21:06 [GIT PULL 1/2] omap soc changes for v3.19 Tony Lindgren
2014-11-14 21:06 ` [GIT PULL 2/2] omap driver " Tony Lindgren
2014-11-14 21:06 ` Tony Lindgren
2014-11-20 11:04 ` Arnd Bergmann
2014-11-20 11:04 ` Arnd Bergmann
2014-11-14 21:06 ` Tony Lindgren
2014-11-20 10:43 ` Arnd Bergmann [this message]
2014-11-20 10:43 ` [GIT PULL 1/2] omap soc " Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2014-11-14 21:06 Tony Lindgren
2014-11-14 21:06 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=201411201143.08649.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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.