linux-kernel - [rfc] Re: [PATCH] Make UIO available for 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]

Date:	Wed, 8 Aug 2007 18:15:21 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Hans-Jürgen Koch <hjk@...utronix.de>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: [rfc] Re: [PATCH] Make UIO available for arm architecture

On Aug 8 2007 18:08, Hans-Jürgen Koch wrote:
>---
>Index: linux-2.6.23-rc/arch/arm/Kconfig
>===================================================================
>--- linux-2.6.23-rc.orig/arch/arm/Kconfig	2007-08-08 17:52:02.000000000 +0200
>+++ linux-2.6.23-rc/arch/arm/Kconfig	2007-08-08 17:53:29.000000000 +0200
>@@ -1052,6 +1052,8 @@
> 
> source "drivers/dma/Kconfig"
> 
>+source "drivers/uio/Kconfig"
>+
> endmenu
> 
> source "fs/Kconfig"

I am raising a general question here.
Should not such cross-platform things be made available in a general
Kconfig rather than having to patch each arch's Kconfig?

I am thinking of drivers/Kconfig for this one (of course I am aware that this
requires an extra "depends on X86 || SPARC || others" in drivers/pci/Kconfig),
and perhaps even a top-level Kconfig for things like truly arch-independent
fs/Kconfig.

	Jan
--