From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: vexpress: Updates for v4.7
Date: Sun, 24 Apr 2016 23:35:07 +0200 [thread overview]
Message-ID: <7123166.4dBrA6hMxj@wuerfel> (raw)
In-Reply-To: <57112A05.3070709@arm.com>
On Friday 15 April 2016 18:51:01 Sudeep Holla wrote:
> This time addition of support for Cortex-M based MPS2 system is
> the main highlight. I could not split the patches into platform,
> driver and DT because it's newly added and have Kconfig/Makefile
> dependency.
I don't get it. Why is there a dependency between the three things?
Usually nothing breaks by adding any of those things, so the only
dependency is that you need them all in order to make the platform
work, but that is not enough reason to put them into a common branch.
Please respin this. When you do, it probably makes sense to
separate the changes for vexpress from the new MPS2 platform
into distinct branches.
I see you got the Acks from the clockevent and serial maintainers,
but I don't see why they did not just merge those.
Arnd
next prev parent reply other threads:[~2016-04-24 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 17:51 [GIT PULL] ARM: vexpress: Updates for v4.7 Sudeep Holla
2016-04-24 21:35 ` Arnd Bergmann [this message]
2016-04-25 9:18 ` Sudeep Holla
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=7123166.4dBrA6hMxj@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