From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Reverting ARCH_SUNXI arm64 support(?)
Date: Mon, 9 May 2016 10:09:52 +0100 [thread overview]
Message-ID: <20160509090951.GC19763@arm.com> (raw)
In-Reply-To: <57304FF7.3080909@arm.com>
On Mon, May 09, 2016 at 09:53:11AM +0100, Andre Przywara wrote:
> Hi Will, Catalin,
Hi Andre,
> Suzuki reported a build failure with certain (non-defconfig) .configs
> due to the new ARCH_SUNXI support in 4.6-rc [1].
> As unfortunately we couldn't agree on a solution and also the support
> for the A64/Pine64 is partial in 4.6 anyway, can you please revert:
> ce3dd55b99b151a90ac1701c6825f2ae2d49b54e ("arm64: Introduce Allwinner
> SoC config option")
Given that we (Catalin and I) didn't commit that patch, it seems weird
that we should be reverting it. Shouldn't this be handled in arm-soc or
via the sunxi subtree?
We're also a week from the merge window, so it doesn't seem like a good
time to be hacking at .config/kconfig-related issues.
Will
next prev parent reply other threads:[~2016-05-09 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 8:53 Reverting ARCH_SUNXI arm64 support(?) Andre Przywara
2016-05-09 9:09 ` Will Deacon [this message]
2016-05-09 11:15 ` Andre Przywara
2016-05-09 20:57 ` Maxime Ripard
2016-05-09 21:03 ` 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=20160509090951.GC19763@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).