public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@dolly1.pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] drivers/Kconfig
Date: Tue, 23 Sep 2003 12:02:36 -0400	[thread overview]
Message-ID: <20030923160236.GA20000@gtf.org> (raw)
In-Reply-To: <20030923152032.GA16599@lst.de>

On Tue, Sep 23, 2003 at 05:20:32PM +0200, Christoph Hellwig wrote:
> What do people think about creating a common drivers/Kconfig
> that includes the drivers/*/Kconfig files?  This saves quite
> a few superflous Kconfig lines and is a natural way to avoid
> the architectyures going out of sync.  Yes, this requires
> every driver having proper bus-depencies but we should be
> almost there already.
> 
> Sample patch (for ppc, i386 and x86_64) attached.  

Yes, this is the goal.

This won't be very useful to the more exotic architectures like S/390,
which use almost none of drivers/* except for drivers/s390/*, so for
non-PCI, non-ISA architectures I have a feeling that including
drivers/Kconfig would be a waste.

	Jeff





      reply	other threads:[~2003-09-23 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23 15:20 [PATCH][RFC] drivers/Kconfig Christoph Hellwig
2003-09-23 16:02 ` Jeff Garzik [this message]

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=20030923160236.GA20000@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=hch@dolly1.pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox