linux-kernel - Re: [PATCH] arm64: Split out platform options to separate Kconfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 17 Jul 2015 10:29:29 -0700
From:	Olof Johansson <olof@...om.net>
To:	Will Deacon <will.deacon@....com>
Cc:	Catalin Marinas <Catalin.Marinas@....com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: Split out platform options to separate Kconfig

On Wed, Jul 15, 2015 at 02:01:52PM +0100, Will Deacon wrote:
> 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@...om.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@....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?

We've been able to avoid most of these conflicts so far, haven't
we? Hopefully it'll be fairly limited. We don't want to hold off touching
defconfig until -rc1 since it means no build/test coverage until after
the merge window closes.  So hopefully we can just deal with it as it
comes up.


-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/