public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round)
Date: Fri, 18 Mar 2016 17:49 +0100	[thread overview]
Message-ID: <3064565.apY2TeQbln@wuerfel> (raw)
In-Reply-To: <CAK7LNARW9u=btLwc9Pj3VFx_q_unfWu9gH4sHNC3-9gLd0p=pg@mail.gmail.com>

On Tuesday 15 March 2016 11:01:00 Masahiro Yamada wrote:
> Olof, Arnd,
> 
> 
> I sent my patches around -rc4 and
> took action soon as requested.
> 
> But, my series is still not applied due to the long silence on your side.
> 
> Please respond!

Sorry for all the delays, we screwed this one up, and you did everything
right. I have put the DT changes into the next/dt2 branch now, and applied
the two other patches to next/soc directly.

Please check that the for-next branch in arm-soc has everything you need now.

	Arnd

  reply	other threads:[~2016-03-18 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  7:16 [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round) Masahiro Yamada
2016-02-26  7:16 ` [PATCH 1/2] ARM: uniphier: add missing of_node_put() Masahiro Yamada
2016-02-26  7:16 ` [PATCH 2/2] ARM: uniphier: rework SMP code to support new System Bus binding Masahiro Yamada
2016-03-07  9:30 ` [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round) Masahiro Yamada
2016-03-12 23:42   ` Masahiro Yamada
2016-03-15  2:01     ` Masahiro Yamada
2016-03-18 16:49       ` Arnd Bergmann [this message]
2016-03-18 23:49         ` Masahiro Yamada
2016-03-21  3:59           ` Masahiro Yamada
2016-03-21  9:49             ` Arnd Bergmann
2016-03-21 12:39               ` Masahiro Yamada
2016-03-21 19:33                 ` 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=3064565.apY2TeQbln@wuerfel \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox