All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: arm@kernel.org, Chen-Yu Tsai <wens@csie.org>,
	Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [GIT PULL] Allwinner DT changes for 4.9, take 2
Date: Tue, 13 Sep 2016 17:53:55 +0200	[thread overview]
Message-ID: <3492284.FjaSmsNYuk@wuerfel> (raw)
In-Reply-To: <20160911204420.GA11949@lukather>

On Sunday, September 11, 2016 10:44:20 PM CEST Maxime Ripard wrote:
> Allwinner DT changes for 4.9, take 2
> 
> A second set of device tree changes, this time switching a few SoCs to the
> new sunxi-ng clock framework. We also added the support for a new SoC
> (NextThing GR8 and its evaluation board), and the support for the DRM
> driver in the A33.
> 
> 

Pulled into *next/late* because of the dependency, rather than next/dt.

I think this is better so we can send off the other next/dt changes
early on during the merge window without considering the dependency.

If the clk git gets sent before our pull requests, we might just
merge next/late back into next/dt.

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] Allwinner DT changes for 4.9, take 2
Date: Tue, 13 Sep 2016 17:53:55 +0200	[thread overview]
Message-ID: <3492284.FjaSmsNYuk@wuerfel> (raw)
In-Reply-To: <20160911204420.GA11949@lukather>

On Sunday, September 11, 2016 10:44:20 PM CEST Maxime Ripard wrote:
> Allwinner DT changes for 4.9, take 2
> 
> A second set of device tree changes, this time switching a few SoCs to the
> new sunxi-ng clock framework. We also added the support for a new SoC
> (NextThing GR8 and its evaluation board), and the support for the DRM
> driver in the A33.
> 
> 

Pulled into *next/late* because of the dependency, rather than next/dt.

I think this is better so we can send off the other next/dt changes
early on during the merge window without considering the dependency.

If the clk git gets sent before our pull requests, we might just
merge next/late back into next/dt.

Thanks,

	Arnd

  reply	other threads:[~2016-09-13 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 20:44 [GIT PULL] Allwinner DT changes for 4.9, take 2 Maxime Ripard
2016-09-11 20:44 ` Maxime Ripard
2016-09-13 15:53 ` Arnd Bergmann [this message]
2016-09-13 15:53   ` 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=3492284.FjaSmsNYuk@wuerfel \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=wens@csie.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.