linux-kernel - Re: Use of drivers/platform and matching include?

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131004114340.GM12758@n2100.arm.linux.org.uk>
Date:	Fri, 4 Oct 2013 12:43:40 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Olof Johansson <olof@...om.net>, linux-arm-msm@...r.kernel.org,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Kumar Gala <galak@...eaurora.org>
Subject: Re: Use of drivers/platform and matching include?

On Thu, Oct 03, 2013 at 10:09:14AM -0700, Greg Kroah-Hartman wrote:
> On Thu, Oct 03, 2013 at 09:46:30AM -0700, Olof Johansson wrote:
> > I don't have a good answer though. If it wasn't for the arm64 fork,
> > locating these under arch/arm somewhere would really be the reasonable
> > answer, like we used to do on powerpc. :(
> 
> Sounds like yet-another-good reason why there shouldn't be an arm64
> "fork" at all :(
> 
> The arm community created this mess, you all can fix it up, it's not too
> late.

I said at the time, way before arm64 was merged that it should not be a
separate arch.  Every bit of feedback I gave on arm64 got shouted down
by Catalin.  ARM64 is Catalin's baby and he wants to protect it at all
costs.  I'm surprised Linus even pulled it in with no argument.
--
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/