[PATCH 0/2] arm64: first set of Kconfig patches for Tegra132 support

[Catalin Marinas]

On Wed, Jan 07, 2015 at 02:54:23PM +0000, Will Deacon wrote:
> On Wed, Jan 07, 2015 at 02:25:21PM +0000, Thierry Reding wrote:
> > On Wed, Jan 07, 2015 at 11:07:38AM +0000, Will Deacon wrote:
> > > On Wed, Jan 07, 2015 at 08:17:29AM +0000, Paul Walmsley wrote:
> > > > These patches start the ARM64 Kconfig and defconfig changes to
> > > > support the Tegra132 (aka Tegra K1 64-bit) SoC and the NVIDIA
> > > > Norrin64 FFD board.
> > > > 
> > > > Tegra132 support is made conditional on CONFIG_BROKEN, since
> > > > there are some patches pending for other maintainers to fix
> > > > compilation when CONFIG_ARCH_TEGRA is set during an ARM64 build.
> > > > Once those patches have been merged, a subsequent patch will be
> > > > sent to remove the CONFIG_BROKEN dependency and to make a few other
> > > > defconfig changes that are dependent on CONFIG_ARCH_TEGRA.
> > > > 
> > > > These patches apply on the arm64 fixes/core branch, commit
> > > > 5d96e0cba263.  They have been boot-tested on QEMU 2.2.0 AArch64,
> > > > and (after other patches have been applied) have been boot-tested
> > > > on the Tegra132 Norrin64 FFD board.
> > > 
> > > Whilst I'm happy to take the second patch for 3.20 (getting those
> > > dependencies building and keeping them building is a Good Thing), can we
> > > hold off on the first patch until it's not broken? Having an unconditional
> > > depends on BROKEN isn't really that useful.
> > 
> > The two patches that require the BROKEN dependency are fairly trivial,
> > so I don't think it would be a stretch to merge them for 3.20. But they
> > apply to different trees (one to the clocksource tree, the other to the
> > Tegra tree).
> > 
> > How do you usually handle the ARM64 patches? Do you manually pick up the
> > patches that touch arch/arm64 or would you prefer for me to collect them
> > in a pull request?
> 
> Either is fine; if it's a large series then a pull request tends to work
> better. Catalin is handling the 3.20 merge window (we take it in turns).

Indeed, for 2-3 patches, I just cherry-pick them (but not before cursing
the email system for corrupting the patches).

-- 
Catalin