All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm Kconfig fixes
Date: Sat, 28 Aug 2004 22:05:33 +0100	[thread overview]
Message-ID: <20040828210533.GD6301@redhat.com> (raw)
In-Reply-To: <200408280309.i7S39PPv000756@hera.kernel.org>

On Sat, Aug 28, 2004 at 02:13:44AM +0000, Linux Kernel wrote:
 > ChangeSet 1.1892, 2004/08/27 19:13:44-07:00, viro@www.linux.org.uk
 > 
 > 	[PATCH] arm Kconfig fixes
 > 	
 > 	ARM dependency and makefile fixes (ACKed by rmk)
 > 	
 > diff -Nru a/drivers/char/agp/Kconfig b/drivers/char/agp/Kconfig
 > --- a/drivers/char/agp/Kconfig	2004-08-27 20:09:34 -07:00
 > +++ b/drivers/char/agp/Kconfig	2004-08-27 20:09:34 -07:00
 > @@ -1,5 +1,5 @@
 >  config AGP
 > -	tristate "/dev/agpgart (AGP Support)" if !GART_IOMMU && !M68K
 > +	tristate "/dev/agpgart (AGP Support)" if !GART_IOMMU && !M68K && !ARM
 >  	default y if GART_IOMMU
 >  	---help---
 >  	  AGP (Accelerated Graphics Port) is a bus system mainly used to

This has the opportunity to grow and grow and make things really ugly
in all the driver specific Kconfigs each time a new arch switches
over to use drivers/Kconfig.  Is this really any better than doing
this checking in drivers/Kconfig itself and keeping the subdir'd kconfig's
somewhat cleaner ?

Even if not,  I think I'd actually prefer a whitelist of drivers that *do*
support agpgart in the Kconfig, than the above which needs to be added to
all the time.  Something like if X86 && ALPHA && IA64 should cover it currently.
It just seems to me to be a lot more sensible than listing a bunch
of stuff which is completely irrelevant.

		Dave


       reply	other threads:[~2004-08-28 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200408280309.i7S39PPv000756@hera.kernel.org>
2004-08-28 21:05 ` Dave Jones [this message]
2004-08-28 21:13   ` [PATCH] arm Kconfig fixes Christoph Hellwig
2004-08-28 21:17     ` Dave Jones
2004-08-28 21:22       ` Christoph Hellwig
2004-08-28 21:43         ` viro
2004-08-31 12:07           ` Roman Zippel

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=20040828210533.GD6301@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.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.