From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas ARM Based SoC Fixes for v3.14
Date: Wed, 15 Jan 2014 00:04:29 +0000 [thread overview]
Message-ID: <20140115000429.GF8769@verge.net.au> (raw)
In-Reply-To: <87a9ey8kt5.fsf@linaro.org>
On Tue, Jan 14, 2014 at 10:44:54AM -0800, Kevin Hilman wrote:
> Simon Horman <horms+renesas@verge.net.au> writes:
>
> > Hi Olof, Hi Kevin, Hi Arnd,
> >
> > please consider these renesas ARM Based SoC Fixes for v3.14.
> >
> > This pull-request is based on the Third Round of Renesas ARM Based SoC
> > Updates for v3.14, tagged as renesas-soc3-for-v3.14, which you have
> > previously pulled.
> >
> > It resolves a problem introduced by a patch included in the second round of such
> > changes, tagged as renesas-soc2-for-v3.14, which you have also previously
> > pulled.
> >
> > renesas-soc3-for-v3.14 is based on renesas-soc2-for-v3.14.
>
> Applied.
>
> Since your soc3 branch was included in our next/soc branch, I've just
> added the fix there as well.
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Fixes for v3.14
Date: Wed, 15 Jan 2014 09:04:29 +0900 [thread overview]
Message-ID: <20140115000429.GF8769@verge.net.au> (raw)
In-Reply-To: <87a9ey8kt5.fsf@linaro.org>
On Tue, Jan 14, 2014 at 10:44:54AM -0800, Kevin Hilman wrote:
> Simon Horman <horms+renesas@verge.net.au> writes:
>
> > Hi Olof, Hi Kevin, Hi Arnd,
> >
> > please consider these renesas ARM Based SoC Fixes for v3.14.
> >
> > This pull-request is based on the Third Round of Renesas ARM Based SoC
> > Updates for v3.14, tagged as renesas-soc3-for-v3.14, which you have
> > previously pulled.
> >
> > It resolves a problem introduced by a patch included in the second round of such
> > changes, tagged as renesas-soc2-for-v3.14, which you have also previously
> > pulled.
> >
> > renesas-soc3-for-v3.14 is based on renesas-soc2-for-v3.14.
>
> Applied.
>
> Since your soc3 branch was included in our next/soc branch, I've just
> added the fix there as well.
Thanks.
next prev parent reply other threads:[~2014-01-15 0:04 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 2:45 [GIT PULL] Renesas ARM Based SoC Fixes for v3.14 Simon Horman
2014-01-10 2:45 ` Simon Horman
2014-01-10 2:46 ` [PATCH] ARM: shmobile: r8a7790: Fix I2C controller names Simon Horman
2014-01-10 2:46 ` Simon Horman
2014-01-14 18:44 ` [GIT PULL] Renesas ARM Based SoC Fixes for v3.14 Kevin Hilman
2014-01-14 18:44 ` Kevin Hilman
2014-01-15 0:04 ` Simon Horman [this message]
2014-01-15 0:04 ` Simon Horman
2014-05-29 23:31 ` [GIT PULL] Renesas ARM Based SoC Fixes for v3.16 Simon Horman
2014-05-29 23:31 ` Simon Horman
2014-05-29 23:31 ` [PATCH] ARM: shmobile: armadillo800eva: fixup HDMI sound flags setting Simon Horman
2014-05-29 23:31 ` Simon Horman
2014-05-30 16:23 ` [GIT PULL] Renesas ARM Based SoC Fixes for v3.16 Olof Johansson
2014-05-30 16:23 ` Olof Johansson
2014-11-17 2:45 ` [GIT PULL] Renesas ARM Based SoC Fixes for v3.18 Simon Horman
2014-11-17 2:45 ` Simon Horman
2014-11-17 2:45 ` [PATCH] ARM: shmobile: kzm9g legacy: Set i2c clks_per_count to 2 Simon Horman
2014-11-17 2:45 ` Simon Horman
2015-01-13 2:13 ` [GIT PULL] Renesas ARM Based SoC Fixes for v3.19 Simon Horman
2015-01-13 2:13 ` Simon Horman
2015-01-13 2:13 ` [PATCH 1/2] ARM: shmobile: r8a7740: Instantiate GIC from C board code in legacy builds Simon Horman
2015-01-13 2:13 ` Simon Horman
2015-01-13 2:13 ` [PATCH 2/2] ARM: shmobile: sh73a0 legacy: Set .control_parent for all irqpin instances Simon Horman
2015-01-13 2:13 ` Simon Horman
2015-01-13 8:10 ` [GIT PULL] Renesas ARM Based SoC Fixes for v3.19 Geert Uytterhoeven
2015-01-13 8:10 ` Geert Uytterhoeven
2015-01-13 23:32 ` Olof Johansson
2015-01-13 23:32 ` Olof Johansson
2015-01-14 0:20 ` Simon Horman
2015-01-14 0:20 ` Simon Horman
2015-05-07 5:46 ` [GIT PULL] Renesas ARM Based SoC Fixes for v4.1 Simon Horman
2015-05-07 5:46 ` Simon Horman
2015-05-07 5:46 ` [PATCH] ARM: shmobile: koelsch: Fix adv7511 IRQ sensing Simon Horman
2015-05-07 5:46 ` Simon Horman
2015-05-07 16:27 ` [GIT PULL] Renesas ARM Based SoC Fixes for v4.1 Arnd Bergmann
2015-05-07 16:27 ` Arnd Bergmann
2015-10-02 2:29 ` [GIT PULL] Renesas ARM Based SoC Fixes for v4.3 Simon Horman
2015-10-02 2:29 ` Simon Horman
2015-10-02 2:29 ` [PATCH 1/2] ARM: shmobile: r8a7790 dtsi: Add CPG/MSTP Clock Domain for sound Simon Horman
2015-10-02 2:29 ` Simon Horman
2015-10-02 11:29 ` Sergei Shtylyov
2015-10-02 11:29 ` Sergei Shtylyov
2015-10-02 11:32 ` Sergei Shtylyov
2015-10-02 11:32 ` Sergei Shtylyov
2015-10-06 12:37 ` Arnd Bergmann
2015-10-06 12:37 ` Arnd Bergmann
2015-10-02 2:29 ` [PATCH 2/2] ARM: shmobile: r8a7791 " Simon Horman
2015-10-02 2:29 ` Simon Horman
2015-10-16 14:05 ` [PATCH 2/2] ARM: shmobile: r8a7791 dtsi: Remove bogus imp_clk node Geert Uytterhoeven
2015-10-06 12:32 ` [GIT PULL] Renesas ARM Based SoC Fixes for v4.3 Arnd Bergmann
2015-10-06 12:32 ` Arnd Bergmann
2015-11-27 1:56 ` [GIT PULL] Renesas ARM Based SoC Fixes for v4.4 Simon Horman
2015-11-27 1:56 ` Simon Horman
2015-11-27 1:56 ` [PATCH] ARM: shmobile: r8a7793: proper constness with __initconst Simon Horman
2015-11-27 1:56 ` Simon Horman
2015-11-27 16:30 ` [GIT PULL] Renesas ARM Based SoC Fixes for v4.4 Arnd Bergmann
2015-11-27 16:30 ` Arnd Bergmann
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=20140115000429.GF8769@verge.net.au \
--to=horms@verge.net.au \
--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.