From: Jim Nelson <james4765@verizon.net>
To: Matthew Wilcox <matthew@wil.cx>
Cc: kernel-janitors@lists.osdl.org, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org
Subject: Re: [KJ] [PATCH 7/9] to arch/sparc/Kconfig
Date: Thu, 28 Oct 2004 15:25:26 +0000 [thread overview]
Message-ID: <41810F66.90308@verizon.net> (raw)
In-Reply-To: <20041028151336.GA10769@parcelfarce.linux.theplanet.co.uk>
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
Matthew Wilcox wrote:
> On Thu, Oct 28, 2004 at 10:01:12AM -0500, james4765@verizon.net wrote:
>
>>Description: Add default for SUN4 in arch/sparc/Kconfig.
>>Apply against 2.6.9.
>
>
> The default is already "no". This patch seems pointless.
>
Err, you're right. Unless it is better to have a default on all configuration items.
That'd fix the "# THIS_OPTION is not set" notes in .config, but that's a bit of
heavy lifting, going through all of the Kconfig files.
Opinions?
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
WARNING: multiple messages have this Message-ID (diff)
From: Jim Nelson <james4765@verizon.net>
To: Matthew Wilcox <matthew@wil.cx>
Cc: kernel-janitors@lists.osdl.org, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org
Subject: Re: [KJ] [PATCH 7/9] to arch/sparc/Kconfig
Date: Thu, 28 Oct 2004 11:25:26 -0400 [thread overview]
Message-ID: <41810F66.90308@verizon.net> (raw)
In-Reply-To: <20041028151336.GA10769@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> On Thu, Oct 28, 2004 at 10:01:12AM -0500, james4765@verizon.net wrote:
>
>>Description: Add default for SUN4 in arch/sparc/Kconfig.
>>Apply against 2.6.9.
>
>
> The default is already "no". This patch seems pointless.
>
Err, you're right. Unless it is better to have a default on all configuration items.
That'd fix the "# THIS_OPTION is not set" notes in .config, but that's a bit of
heavy lifting, going through all of the Kconfig files.
Opinions?
next prev parent reply other threads:[~2004-10-28 15:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 15:00 [KJ] [PATCH 1/9] to arch/sh/drivers/pci/Kconfig james4765
2004-10-28 15:00 ` james4765
2004-10-28 15:00 ` [KJ] [PATCH 2/9] to arch/sparc64/Kconfig james4765
2004-10-28 15:00 ` james4765
2004-10-28 15:00 ` [KJ] [PATCH 3/9] " james4765
2004-10-28 15:00 ` james4765
2004-10-28 15:00 ` [KJ] [PATCH 4/9] to arch/sparc/Kconfig james4765
2004-10-28 15:00 ` james4765
2004-10-28 15:00 ` [KJ] [PATCH 5/9] " james4765
2004-10-28 15:00 ` james4765
2004-10-28 15:01 ` [KJ] [PATCH 6/9] " james4765
2004-10-28 15:01 ` james4765
2004-10-28 15:01 ` [KJ] [PATCH 7/9] " james4765
2004-10-28 15:01 ` james4765
2004-10-28 15:13 ` [KJ] " Matthew Wilcox
2004-10-28 15:13 ` Matthew Wilcox
2004-10-28 15:25 ` Jim Nelson [this message]
2004-10-28 15:25 ` Jim Nelson
2004-10-28 15:01 ` [KJ] [PATCH 8/9] " james4765
2004-10-28 15:01 ` james4765
2004-10-28 15:01 ` [KJ] [PATCH 9/9] to kernel/power/Kconfig james4765
2004-10-28 15:01 ` james4765
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=41810F66.90308@verizon.net \
--to=james4765@verizon.net \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rusty@rustcorp.com.au \
/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.