From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Marcin Juszkiewicz <openembedded@haerwu.biz>
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
Christoph Hellwig <hch@infradead.org>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/arm/Kconfig: Make UIO available on ARM architecture
Date: Thu, 7 Feb 2008 16:05:58 +0000 [thread overview]
Message-ID: <20080207160557.GB28435@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200802071609.36960.openembedded@haerwu.biz>
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.
next prev parent reply other threads:[~2008-02-07 16:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 12:38 Hans-Jürgen Koch
2008-02-07 12:58 ` Christoph Hellwig
2008-02-07 13:01 ` Sam Ravnborg
2008-02-07 15:09 ` Marcin Juszkiewicz
2008-02-07 16:05 ` Russell King - ARM Linux [this message]
2008-02-07 20:23 ` Sam Ravnborg
2008-02-07 20:29 ` Russell King - ARM Linux
2008-02-07 21:05 ` Sam Ravnborg
2008-02-08 9:04 ` David Woodhouse
2008-02-08 9:45 ` Russell King - ARM Linux
2008-02-08 10:18 ` David Woodhouse
2008-02-08 10:23 ` Russell King - ARM Linux
2008-02-08 10:43 ` David Woodhouse
2008-02-08 10:45 ` Russell King - ARM Linux
2008-02-12 1:51 ` Greg Ungerer
2008-02-08 10:58 ` David Woodhouse
2008-02-08 18:46 ` Sam Ravnborg
2008-02-08 18:52 ` David Woodhouse
2008-02-09 11:39 ` Sam Ravnborg
2008-02-07 14:21 ` Russell King - ARM Linux
2008-02-07 13:02 ` Russell King - ARM Linux
2008-02-07 13:12 ` Hans-Jürgen Koch
2008-02-11 8:25 ` Hans-Jürgen Koch
2008-02-11 14:39 ` Sam Ravnborg
2008-04-10 12:21 ` Uwe Kleine-König
2008-04-10 12:27 ` Russell King - ARM Linux
2008-04-10 12:57 ` Uwe Kleine-König
2008-04-10 13:10 ` Russell King - ARM Linux
2008-04-10 13:50 ` Uwe Kleine-König
2008-04-10 18:58 ` Sam Ravnborg
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=20080207160557.GB28435@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=openembedded@haerwu.biz \
/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®