From: Greg KH <gregkh@suse.de>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Hans-J?rgen Koch <hjk@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [rfc] Re: [PATCH] Make UIO available for arm architecture
Date: Wed, 8 Aug 2007 09:10:02 -0700 [thread overview]
Message-ID: <20070808161002.GA11153@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708081812250.3715@fbirervta.pbzchgretzou.qr>
On Wed, Aug 08, 2007 at 06:15:21PM +0200, Jan Engelhardt wrote:
>
> 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.
Um, uio _is_ in drivers/Kconfig already :)
But I'm guessing that ARM doesn't use that file yet? If so, I have no
objection to the above patch, but it should go through the ARM
developers, not me.
thanks,
greg k-h
next prev parent reply other threads:[~2007-08-08 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 16:08 Hans-Jürgen Koch
2007-08-08 16:15 ` [rfc] " Jan Engelhardt
2007-08-08 16:10 ` Greg KH [this message]
2007-08-08 16:33 ` Hans-Jürgen Koch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070808161002.GA11153@suse.de \
--to=gregkh@suse.de \
--cc=hjk@linutronix.de \
--cc=jengelh@computergmbh.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®