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

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. :(

Are you seriously suggesting going back to having drivers under arch/arm
because we can't find a home for them in the drivers subtree?

Having made a big thing about things as small as clock source drivers,
IRQ drivers and such like which "shouldn't be under arch/arm" and moving
them out, to then say about finding somewhere under arch/arm for drivers
is very much a case of double-standards.

I've heard this accusation that we have too many drivers in arch/arm
many times, and although we've made some progress getting things like
clock and IRQ drivers out of arch/arm, we're still a long way from
sorting that out.  Or maybe that original accusation was baseless for
modern kernels, based on the old 1.x days when we had a arch/arm/drivers
subdirectory which people have a hard time forgetting?

So, no, there will be no new drivers under arch/arm.  They must be in the
drivers subtree somewhere.
--
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/