From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Split out platform options to separate Kconfig
Date: Wed, 15 Jul 2015 14:01:52 +0100 [thread overview]
Message-ID: <20150715130152.GG1005@arm.com> (raw)
In-Reply-To: <1436958621-23524-1-git-send-email-olof@lixom.net>
Hi Olof,
On Wed, Jul 15, 2015 at 12:10:21PM +0100, Olof Johansson wrote:
> Let's move out the platform Kconfig entries to a separate file, since these
> changes usually get moved through arm-soc instead of the arm64 arch tree, and
> this will lead to fewer conflicts
>
> Signed-off-by: Olof Johansson <olof@lixom.net>
> ---
>
> Will, Catalin, I'll merge this through arm-soc if I get your acks. Thanks!
Fine by me:
Acked-by: Will Deacon <will.deacon@arm.com>
The only problem I can think of is how we resolve defconfig conflicts
between you adding a new platform and us adding a new feature, since
resolving those usually happens by regenerating the defconfig anyway.
Maybe we just wait until -rc1 before adding new platforms to defconfig?
Will
next prev parent reply other threads:[~2015-07-15 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 11:10 [PATCH] arm64: Split out platform options to separate Kconfig Olof Johansson
2015-07-15 13:01 ` Will Deacon [this message]
2015-07-17 17:29 ` Olof Johansson
2015-07-15 13:20 ` Catalin Marinas
2015-07-17 17:27 ` Olof Johansson
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=20150715130152.GG1005@arm.com \
--to=will.deacon@arm.com \
--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).