From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM64 Based SoC DT Updates for v4.10
Date: Fri, 18 Nov 2016 17:41:50 -0800 [thread overview]
Message-ID: <20161119014150.GC2543@localhost> (raw)
In-Reply-To: <cover.1479388193.git.horms+renesas@verge.net.au>
On Thu, Nov 17, 2016 at 03:04:55PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM64 based SoC DT updates
> for v4.10.
>
> This pull request is based on a merge of:
>
> * The previous round of such requests, tagged as renesas-arm64-dt-for-v4.10,
> which I have already sent a pull-request for.
> * The "Second Round of Renesas ARM Based SoC Drivers Updates for v4.10",
> tagged as renesas-drivers2-for-v4.10, which I have also sent a pull
> request for. This is included to provide dependencies for adding device
> nodes for PRR.
Please avoid entangling these pull requests, since now I can't merge DT since
I'm rejecting your drivers pull request.
I also don't understand why you need a driver branch as base. The PRR
nodes are literally just a compatible field and a reg entry. It should
depend on nothing.
So, I'm a little confused here. Please disentangle this and send a separate
pull request, I'll be happy to merge that.
-Olof
next prev parent reply other threads:[~2016-11-19 1:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 14:04 [GIT PULL] Second Round of Renesas ARM64 Based SoC DT Updates for v4.10 Simon Horman
2016-11-17 14:04 ` [PATCH 01/18] arm64: dts: r8a7796: add I2C support Simon Horman
2016-11-17 14:04 ` [PATCH 02/18] arm64: dts: r8a7796: Enable I2C DMA Simon Horman
2016-11-17 14:04 ` [PATCH 03/18] arm64: dts: r8a7796: salvator-x: enable I2C Simon Horman
2016-11-17 14:04 ` [PATCH 04/18] arm64: dts: h3ulcb: update documentation with official board name Simon Horman
2016-11-17 14:04 ` [PATCH 05/18] arm64: dts: h3ulcb: update header Simon Horman
2016-11-17 14:04 ` [PATCH 06/18] arm64: dts: m3ulcb: add M3ULCB board DT bindings Simon Horman
2016-11-17 14:04 ` [PATCH 07/18] arm64: dts: m3ulcb: initial device tree Simon Horman
2016-11-17 14:04 ` [PATCH 08/18] arm64: dts: m3ulcb: enable SCIF clk and pins Simon Horman
2016-11-17 14:04 ` [PATCH 09/18] arm64: dts: m3ulcb: enable GPIO leds Simon Horman
2016-11-17 14:04 ` [PATCH 10/18] arm64: dts: m3ulcb: enable GPIO keys Simon Horman
2016-11-17 14:04 ` [PATCH 11/18] arm64: dts: m3ulcb: enable EXTALR clk Simon Horman
2016-11-17 14:04 ` [PATCH 12/18] arm64: dts: m3ulcb: enable WDT Simon Horman
2016-11-17 14:04 ` [PATCH 13/18] arm64: dts: m3ulcb: enable SDHI0 Simon Horman
2016-11-17 14:04 ` [PATCH 14/18] arm64: dts: m3ulcb: enable SDHI2 Simon Horman
2016-11-17 14:04 ` [PATCH 15/18] arm64: dts: h3ulcb: " Simon Horman
2016-11-17 14:04 ` [PATCH 16/18] arm64: dts: h3ulcb: rename SDHI0 pins Simon Horman
2016-11-17 14:04 ` [PATCH 17/18] arm64: dts: r8a7795: Add device node for PRR Simon Horman
2016-11-17 14:04 ` [PATCH 18/18] arm64: dts: r8a7796: " Simon Horman
2016-11-19 1:41 ` Olof Johansson [this message]
2016-11-21 10:55 ` [GIT PULL] Second Round of Renesas ARM64 Based SoC DT Updates for v4.10 Simon Horman
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=20161119014150.GC2543@localhost \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).