linux-kernel - Re: [PATCH] arch/arm/Kconfig: Make UIO available on ARM architecture

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: <20080207160557.GB28435@flint.arm.linux.org.uk>
Date:	Thu, 7 Feb 2008 16:05:58 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Marcin Juszkiewicz <openembedded@...rwu.biz>
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk,
	Christoph Hellwig <hch@...radead.org>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arch/arm/Kconfig: Make UIO available on ARM architecture

On Thu, Feb 07, 2008 at 04:09:34PM +0100, Marcin Juszkiewicz wrote:
> Dnia Thursday, 7 of February 2008, Sam Ravnborg napisał:
> > On Thu, Feb 07, 2008 at 07:58:24AM -0500, Christoph Hellwig wrote:
> 
> > > Any chance to make arm finally use drivers/Kconfig?  It's a bit silly
> > > that arm still is crapping around while even s390 uses it.
> 
> > rmk said that it should be easy to check the amount of work needed to
> > do so. But I have not had time to look into it yet - hopefully someone
> > in ARM land could fix it.
> 
> I looked at it and 'arch/arm/Kconfig' does not source few entries: 

diff -u arch/arm/Kconfig drivers/Kconfig shows the situation.  This is
why I insist that new entries to arch/arm/Kconfig should be in the same
order as drivers/Kconfig.

> Including of 'drivers/mtd' depends on "ALIGNMENT_TRAP || !CPU_CP15_MMU".

It's this which is the main issue.

> Including of 'drivers/ide' depends on "PCMCIA || ARCH_CLPS7500 || 
> ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_L7200 || 
> ARCH_LH7A40X || ARCH_PXA || ARCH_RPC || ARCH_S3C2410 || ARCH_SA1100 || 
> ARCH_SHARK || FOOTBRIDGE || ARCH_IXP23XX" but 'drivers/ata' (which can be 
> used instead on PCMCIA enabled platforms) does not depend on such set.

IDE people insisted that we _will_ have that silly conditional for IDE.
I personally do not want it and would be happy to see it go - but I
don't have the authority to do that.  Take this one up with Bart.
--
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/