From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Al Boldi <a1426z@gawab.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Can ARM use drivers/Kconfig [Was: Kconfig: Source "drivers/usb/gadget/Kconfig" for ARCH=arm]
Date: Sat, 5 Jan 2008 21:09:17 +0000 [thread overview]
Message-ID: <20080105210917.GC7797@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080105205424.GA10191@uranus.ravnborg.org>
On Sat, Jan 05, 2008 at 09:54:24PM +0100, Sam Ravnborg wrote:
> On Sat, Jan 05, 2008 at 08:31:24PM +0000, Russell King wrote:
> > Not everything in drivers/ is suitable for every ARM configuration. It
> > was felt at the time better for ARM to remain separate because people
> > didn't want to pollute drivers/Kconfig with the ARM specific conditionals.
> >
> Today we would have used HAVE_ for the problematic parts and thus
> it would have been easy to not select what ARM does not support.
> But unfortunately thats not how it got designed.
>
>
> It would be nice to revist one day to see how much is actually needed
> to cleanly supprt ARM in drivers/Kconfig.
You could diff the two Kconfig files - I try to keep them so they list
the same Kconfigs in the same order to keep the diff size down.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-01-05 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 15:42 [PATCH 4/5] USB Kconfig: Source "drivers/usb/gadget/Kconfig" for ARCH=arm Al Boldi
2008-01-05 18:46 ` David Brownell
2008-01-05 19:20 ` Can ARM use drivers/Kconfig [Was: Kconfig: Source "drivers/usb/gadget/Kconfig" for ARCH=arm] Sam Ravnborg
2008-01-05 20:31 ` Russell King
2008-01-05 20:54 ` Sam Ravnborg
2008-01-05 21:09 ` Russell King [this message]
2008-01-05 22:09 ` Arnd Bergmann
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=20080105210917.GC7797@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sam@ravnborg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.