All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas SoC Clock Cleanups for v3.1
Date: Wed, 21 May 2014 21:07:25 +0000	[thread overview]
Message-ID: <20140521210725.GC24341@quad.lixom.net> (raw)
In-Reply-To: <cover.1399967755.git.horms+renesas@verge.net.au>

On Tue, May 13, 2014 at 05:03:41PM +0900, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
> 
> Please consider these Renesas SoC Clock Cleanups for v3.16.
> 
> This pull request is based a merge of the following to provide dependencies
> and avoid conflicts.
> 
> * Renesas ARM Based SoC Board Updates for v3.16,
>   tagged as renesas-boards-for-v3.16, which you have already pulled.
> 
> * Renesas ARM Based SoC Clock Updates for v3.16,
>   tagged as renesas-clock-for-v3.16, which you have already pulled.
> 
> * The cmt-mtu2-tmu-cleanups-for-v3.16 branch of
>   Daniel Lezcano's tree.
> 
>   git://git.linaro.org/people/daniel.lezcano/linux.git clockevents/cmt-mtu2-tmu-cleanups
> 
> 
> The following changes since commit 1c41ecb60b3de08d341be13de1dfc3d907b82694:
> 
>   Merge branch 'clockevents/cmt-mtu2-tmu-cleanups' of git://git.linaro.org/people/daniel.lezcano/linux into cmt-mtu2-tmu-cleanups-for-v3.16 (2014-04-23 10:01:02 +0900)
> 
> are available in the git repository at:
> 
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-clock-cleanup2-for-v3.16

Merged into next/boards due to dependencies.


-Olof

WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas SoC Clock Cleanups for v3.1
Date: Wed, 21 May 2014 14:07:25 -0700	[thread overview]
Message-ID: <20140521210725.GC24341@quad.lixom.net> (raw)
In-Reply-To: <cover.1399967755.git.horms+renesas@verge.net.au>

On Tue, May 13, 2014 at 05:03:41PM +0900, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
> 
> Please consider these Renesas SoC Clock Cleanups for v3.16.
> 
> This pull request is based a merge of the following to provide dependencies
> and avoid conflicts.
> 
> * Renesas ARM Based SoC Board Updates for v3.16,
>   tagged as renesas-boards-for-v3.16, which you have already pulled.
> 
> * Renesas ARM Based SoC Clock Updates for v3.16,
>   tagged as renesas-clock-for-v3.16, which you have already pulled.
> 
> * The cmt-mtu2-tmu-cleanups-for-v3.16 branch of
>   Daniel Lezcano's tree.
> 
>   git://git.linaro.org/people/daniel.lezcano/linux.git clockevents/cmt-mtu2-tmu-cleanups
> 
> 
> The following changes since commit 1c41ecb60b3de08d341be13de1dfc3d907b82694:
> 
>   Merge branch 'clockevents/cmt-mtu2-tmu-cleanups' of git://git.linaro.org/people/daniel.lezcano/linux into cmt-mtu2-tmu-cleanups-for-v3.16 (2014-04-23 10:01:02 +0900)
> 
> are available in the git repository at:
> 
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-clock-cleanup2-for-v3.16

Merged into next/boards due to dependencies.


-Olof

  parent reply	other threads:[~2014-05-21 21:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13  8:03 [GIT PULL] Renesas SoC Clock Cleanups for v3.1 Simon Horman
2014-05-13  8:03 ` Simon Horman
2014-05-13  8:03 ` [PATCH 01/15] sh: Switch to new style CMT device Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 02/15] ARM: shmobile: sh7372: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 03/15] ARM: shmobile: sh73a0: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 04/15] ARM: shmobile: r8a73a4: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 05/15] ARM: shmobile: r8a7740: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 06/15] ARM: shmobile: r8a7790: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 07/15] ARM: shmobile: r8a7791: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 08/15] sh: Switch to new style TMU device Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 09/15] ARM: shmobile: sh7372: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 10/15] ARM: shmobile: sh73a0: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 11/15] ARM: shmobile: r8a7740: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 12/15] ARM: shmobile: r8a7778: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 13/15] ARM: shmobile: r8a7779: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 14/15] sh: Switch to new style MTU2 device Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-13  8:03 ` [PATCH 15/15] ARM: shmobile: r7s72100: " Simon Horman
2014-05-13  8:03   ` Simon Horman
2014-05-16  0:51 ` [GIT PULL] Renesas SoC Clock Cleanups for v3.16 Simon Horman
2014-05-16  0:51   ` Simon Horman
2014-05-20  5:38 ` [GIT PULL] Renesas SoC Clock Cleanups for v3.1 Olof Johansson
2014-05-20  5:38   ` Olof Johansson
2014-05-20 13:01   ` Daniel Lezcano
2014-05-20 13:01     ` Daniel Lezcano
2014-05-21 20:53     ` Olof Johansson
2014-05-21 20:53       ` Olof Johansson
2014-05-21 21:07 ` Olof Johansson [this message]
2014-05-21 21:07   ` Olof Johansson

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=20140521210725.GC24341@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.