From: Olof Johansson <olof@lixom.net>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: arm@kernel.org, linux-renesas-soc@vger.kernel.org,
Kevin Hilman <khilman@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [GIT PULL] Renesas ARM Based SoC EtherAVB Updates for v4.10
Date: Fri, 18 Nov 2016 17:43:27 -0800 [thread overview]
Message-ID: <20161119014327.GD2543@localhost> (raw)
In-Reply-To: <cover.1479390880.git.horms+renesas@verge.net.au>
On Thu, Nov 17, 2016 at 03:05:08PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC EtherAVB updates for v4.10.
>
> This pull request is based on the "Second Round of Renesas ARM64 Based SoC
> DT Updates for v4.10", tagged as arm64-dt-for-v4.10, which I have also sent
> a pull-request for.
>
> The reason for this base is to provide dependencies. For the same reason
> an ack has been provided by David Miller to facilitate a merge of the patch
> via the Renesas tree.
And now we have cascading dependencies. Can't merge this either.
Why is the DT branch and this driver branch entangled?! Again, there is
absolutely no functional dependency between them.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC EtherAVB Updates for v4.10
Date: Fri, 18 Nov 2016 17:43:27 -0800 [thread overview]
Message-ID: <20161119014327.GD2543@localhost> (raw)
In-Reply-To: <cover.1479390880.git.horms+renesas@verge.net.au>
On Thu, Nov 17, 2016 at 03:05:08PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC EtherAVB updates for v4.10.
>
> This pull request is based on the "Second Round of Renesas ARM64 Based SoC
> DT Updates for v4.10", tagged as arm64-dt-for-v4.10, which I have also sent
> a pull-request for.
>
> The reason for this base is to provide dependencies. For the same reason
> an ack has been provided by David Miller to facilitate a merge of the patch
> via the Renesas tree.
And now we have cascading dependencies. Can't merge this either.
Why is the DT branch and this driver branch entangled?! Again, there is
absolutely no functional dependency between them.
-Olof
next prev parent reply other threads:[~2016-11-19 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 14:05 [GIT PULL] Renesas ARM Based SoC EtherAVB Updates for v4.10 Simon Horman
2016-11-17 14:05 ` Simon Horman
2016-11-17 14:05 ` [PATCH] ravb: Support 1Gbps on R-Car H3 ES1.1+ and R-Car M3-W Simon Horman
2016-11-17 14:05 ` Simon Horman
2016-11-19 1:43 ` Olof Johansson [this message]
2016-11-19 1:43 ` [GIT PULL] Renesas ARM Based SoC EtherAVB Updates for v4.10 Olof Johansson
2016-11-21 10:55 ` Simon Horman
2016-11-21 10:55 ` 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=20161119014327.GD2543@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=horms+renesas@verge.net.au \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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.