From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Olof Johansson <olof@lixom.net>,
Simon Horman <horms+renesas@verge.net.au>,
Kevin Hilman <khilman@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org, arm@kernel.org
Subject: Re: [GIT PULL] Second Round of Renesas ARM Based SoC Drivers Updates for v4.10
Date: Wed, 23 Nov 2016 12:43:17 +0100 [thread overview]
Message-ID: <4069888.eCuRFVJTuP@wuerfel> (raw)
In-Reply-To: <20161119013551.GB2543@localhost>
On Friday, November 18, 2016 5:35:51 PM CET Olof Johansson wrote:
>
> So, this pull request contains 8 patches, not 4. Seems like your pull
> request doesn't show any of the code from Geert's branch, didn't mention
> it in the tag and only in the email text above. Furthermore, Geert's
> branch modifies driver core code, so it's extra important to make sure
> it's clear that it's an unusual pull request.
>
> Given that this modifies driver core, please either merge that code
> through Greg first, or get an ack from him. If you merge through him,
> make sure it's on a standalone topic branch that we can share.
As discussed on IRC, I think it makes sense to track that branch
separately in arm-soc, as its own top-level next/* branch.
The branch was first merged into the mmc tree after we got consensus
on the approach.
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] Second Round of Renesas ARM Based SoC Drivers Updates for v4.10
Date: Wed, 23 Nov 2016 12:43:17 +0100 [thread overview]
Message-ID: <4069888.eCuRFVJTuP@wuerfel> (raw)
In-Reply-To: <20161119013551.GB2543@localhost>
On Friday, November 18, 2016 5:35:51 PM CET Olof Johansson wrote:
>
> So, this pull request contains 8 patches, not 4. Seems like your pull
> request doesn't show any of the code from Geert's branch, didn't mention
> it in the tag and only in the email text above. Furthermore, Geert's
> branch modifies driver core code, so it's extra important to make sure
> it's clear that it's an unusual pull request.
>
> Given that this modifies driver core, please either merge that code
> through Greg first, or get an ack from him. If you merge through him,
> make sure it's on a standalone topic branch that we can share.
As discussed on IRC, I think it makes sense to track that branch
separately in arm-soc, as its own top-level next/* branch.
The branch was first merged into the mmc tree after we got consensus
on the approach.
Arnd
next prev parent reply other threads:[~2016-11-23 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 14:04 [GIT PULL] Second Round of Renesas ARM Based SoC Drivers Updates for v4.10 Simon Horman
2016-11-17 14:04 ` Simon Horman
2016-11-17 14:04 ` [PATCH 1/4] ARM: shmobile: r8a7745: add power domain index macros Simon Horman
2016-11-17 14:04 ` Simon Horman
2016-11-17 14:04 ` [PATCH 2/4] soc: renesas: rcar-sysc: add R8A7745 support Simon Horman
2016-11-17 14:04 ` Simon Horman
2016-11-17 14:04 ` [PATCH 3/4] ARM: shmobile: Document DT bindings for Product Register Simon Horman
2016-11-17 14:04 ` Simon Horman
2016-11-17 14:04 ` [PATCH 4/4] soc: renesas: Identify SoC and register with the SoC bus Simon Horman
2016-11-17 14:04 ` Simon Horman
2016-11-19 1:35 ` [GIT PULL] Second Round of Renesas ARM Based SoC Drivers Updates for v4.10 Olof Johansson
2016-11-19 1:35 ` Olof Johansson
2016-11-21 10:16 ` Geert Uytterhoeven
2016-11-21 10:16 ` Geert Uytterhoeven
2016-11-23 11:43 ` Arnd Bergmann [this message]
2016-11-23 11:43 ` 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=4069888.eCuRFVJTuP@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--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 \
--cc=olof@lixom.net \
/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.