public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Kconfig cleanup, part 1
Date: Fri, 16 Jan 2004 19:16:50 +0000	[thread overview]
Message-ID: <16392.14498.812148.896936@napali.hpl.hp.com> (raw)
In-Reply-To: <200401161136.37066.bjorn.helgaas@hp.com>


  Bjorn> arch/ia64/Kconfig has accumulated a lot of cruft.  Here's a
  Bjorn> fairly straightforward 2.6 patch that corrects some typos,
  Bjorn> makes the style a little more consistent, and moves a couple
  Bjorn> items under the options they're dependent on (NR_CPUS goes
  Bjorn> under SMP, for instance).

  Bjorn> I'd really like to do a more extensive cleanup along the
  Bjorn> lines of Matthew Wilcox's patch:

  Bjorn>     http://linux.bkbits.net:8080/linux-2.5/cset@1.1296.78.7

  Bjorn> but I'm not sure how people feel about this during 2.6.

If it results in better/working help text and makes it easier to
configure a working kernel, it makes a lot of sense for 2.6.

I don't suppose I could interest you in making "allmodconfig" work on
ia64?  That's useful for testing purposes.  "allyesconfig" is probably
rather hopeless, because the resulting kernel would be too big to link
(and doesn't really make sense anyhow).

	--david

  reply	other threads:[~2004-01-16 19:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 18:36 [PATCH] Kconfig cleanup, part 1 Bjorn Helgaas
2004-01-16 19:16 ` David Mosberger [this message]
2004-01-16 21:39 ` Peter Chubb
2004-01-16 22:32 ` Bjorn Helgaas
2004-01-16 23:35 ` Matthew Wilcox
2004-01-17  0:03 ` Bjorn Helgaas
2004-01-17  0:18 ` Matthew Wilcox
2004-01-17  0:22 ` Bjorn Helgaas
2004-01-17  0:45 ` Matthew Wilcox
2004-01-17  0:59 ` David Mosberger
2004-01-20 17:11 ` Bjorn Helgaas

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=16392.14498.812148.896936@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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