All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas ARM Based SoC Clock Fixes for v3.18
Date: Wed, 19 Nov 2014 21:20:20 +0000	[thread overview]
Message-ID: <201411192220.20365.arnd@arndb.de> (raw)
In-Reply-To: <cover.1415757100.git.horms+renesas@verge.net.au>

On Thursday 13 November 2014, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
> 
> Please consider these Renesas ARM based SoC clock fixes for v3.18.
> Or alternatively for v3.19 if you feel they are too late for v3.18.
> 

I've merged all three 'fixes' pull requests you had into the fixes
branch:

Renesas ARM Based SoC Clock Fixes for v3.18
Renesas ARM Based SoC DT Fixes for v3.18
Renesas ARM Based SoC Fixes for v3.18

I'm still waiting for a reply from Olof, since he seems to have
skipped them last week when he sent the fixes pull request to Linus.
If he had already decided to postpone the branches for 3.19, I'll
just undo the merge here and put it into next/fixes-non-critical
instead, I'm fine with it either way.

	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] Renesas ARM Based SoC Clock Fixes for v3.18
Date: Wed, 19 Nov 2014 22:20:20 +0100	[thread overview]
Message-ID: <201411192220.20365.arnd@arndb.de> (raw)
In-Reply-To: <cover.1415757100.git.horms+renesas@verge.net.au>

On Thursday 13 November 2014, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
> 
> Please consider these Renesas ARM based SoC clock fixes for v3.18.
> Or alternatively for v3.19 if you feel they are too late for v3.18.
> 

I've merged all three 'fixes' pull requests you had into the fixes
branch:

Renesas ARM Based SoC Clock Fixes for v3.18
Renesas ARM Based SoC DT Fixes for v3.18
Renesas ARM Based SoC Fixes for v3.18

I'm still waiting for a reply from Olof, since he seems to have
skipped them last week when he sent the fixes pull request to Linus.
If he had already decided to postpone the branches for 3.19, I'll
just undo the merge here and put it into next/fixes-non-critical
instead, I'm fine with it either way.

	Arnd

  parent reply	other threads:[~2014-11-19 21:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25  1:09 [GIT PULL] Renesas ARM Based SoC Clock Fixes For v3.17 Simon Horman
2014-08-25  1:09 ` Simon Horman
2014-08-25  1:09 ` [PATCH 1/3] ARM: shmobile: sh73a0: Remove spurious 0x from SCIFB clock name Simon Horman
2014-08-25  1:09   ` Simon Horman
2014-08-25  1:09 ` [PATCH 2/3] ARM: shmobile: r8a7790: add missing 0x0100 for SDCKCR Simon Horman
2014-08-25  1:09   ` Simon Horman
2014-08-25  1:09 ` [PATCH 3/3] ARM: shmobile: r8a7791: " Simon Horman
2014-08-25  1:09   ` Simon Horman
2014-08-26  9:09 ` [GIT PULL] Renesas ARM Based SoC Clock Fixes For v3.17 Simon Horman
2014-08-26  9:09   ` Simon Horman
2014-08-27 22:15 ` Olof Johansson
2014-08-27 22:15   ` Olof Johansson
2014-11-13  1:19 ` [GIT PULL] Renesas ARM Based SoC Clock Fixes for v3.18 Simon Horman
2014-11-13  1:19   ` Simon Horman
2014-11-13  1:19   ` [PATCH 1/3] ARM: shmobile: r8a7790: Fix SD3CKCR address Simon Horman
2014-11-13  1:19     ` Simon Horman
2014-11-13  1:19   ` [PATCH 2/3] ARM: shmobile: r8a7740 legacy: Add missing INTCA clock for irqpin module Simon Horman
2014-11-13  1:19     ` Simon Horman
2014-11-13  1:19   ` [PATCH 3/3] ARM: shmobile: r8a7740 legacy: Correct IIC0 parent clock Simon Horman
2014-11-13  1:19     ` Simon Horman
2014-11-19 21:20   ` Arnd Bergmann [this message]
2014-11-19 21:20     ` [GIT PULL] Renesas ARM Based SoC Clock Fixes for v3.18 Arnd Bergmann
2014-11-20  0:22     ` Simon Horman
2014-11-20  0:22       ` Simon Horman
2014-11-20  8:56     ` Geert Uytterhoeven
2014-11-20  8:56       ` Geert Uytterhoeven

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=201411192220.20365.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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.