From: Tom Rini <trini@kernel.crashing.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.0-test10
Date: Tue, 31 Oct 2000 19:18:07 -0700 [thread overview]
Message-ID: <20001031191807.A32641@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.10.10010311237430.22165-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10010311237430.22165-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Tue, Oct 31, 2000 at 12:41:55PM -0800
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
On Tue, Oct 31, 2000 at 12:41:55PM -0800, Linus Torvalds wrote:
> Ok, test10-final is out there now. This has no _known_ bugs that I
> consider show-stoppers, for what it's worth.
Sure, it's not a critical bug or anything but hey. One more time:
This is a very minor patch for fs/nls/Config.in, which Petr Vandrovec came up
with. The problem is that if CONFIG_INET is n, CONFIG_SMB_FS is never set
so fs/nls/Config.in assumes that the user wants to select some NLS options.
This fixes it and works on config/menuconfig/xconfig.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
[-- Attachment #2: nls.patch --]
[-- Type: text/plain, Size: 601 bytes --]
--- fs/nls/Config.in.orig Thu Oct 19 12:54:09 2000
+++ fs/nls/Config.in Thu Oct 19 12:54:32 2000
@@ -2,10 +2,17 @@
# Native language support configuration
#
+# smb wants NLS
+if [ "$CONFIG_SMB_FS" = "m" -o "$CONFIG_SMB_FS" = "y" ]; then
+ define_bool CONFIG_SMB_NLS y
+else
+ define_bool CONFIG_SMB_NLS n
+fi
+
# msdos and Joliet want NLS
if [ "$CONFIG_JOLIET" = "y" -o "$CONFIG_FAT_FS" != "n" \
-o "$CONFIG_NTFS_FS" != "n" -o "$CONFIG_NCPFS_NLS" = "y" \
- -o "$CONFIG_SMB_FS" != "n" ]; then
+ -o "$CONFIG_SMB_NLS" = "y" ]; then
define_bool CONFIG_NLS y
else
define_bool CONFIG_NLS n
next prev parent reply other threads:[~2000-11-01 2:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-31 20:41 Linux-2.4.0-test10 Linus Torvalds
2000-10-31 20:48 ` Linux-2.4.0-test10 Rik van Riel
2000-10-31 20:57 ` Linux-2.4.0-test10 Linus Torvalds
2000-11-01 5:40 ` Linux-2.4.0-test10 adrian
2000-10-31 20:55 ` Linux-2.4.0-test10 Alan Cox
2000-11-01 1:35 ` Linux-2.4.0-test10 Paul Jakma
2000-11-01 3:53 ` Linux-2.4.0-test10 Jeremy Fitzhardinge
2000-11-01 8:38 ` Linux-2.4.0-test10 Andi Kleen
2000-11-01 18:08 ` Linux-2.4.0-test10 kuznet
2000-11-02 0:03 ` Linux-2.4.0-test10 Jeff Garzik
2000-11-01 23:52 ` Linux-2.4.0-test10 David S. Miller
2000-11-02 17:17 ` Linux-2.4.0-test10 Stephen C. Tweedie
2000-11-02 17:36 ` Linux-2.4.0-test10 Christoph Rohland
2000-11-03 19:18 ` Linux-2.4.0-test10 Pavel Machek
2000-11-04 18:49 ` Linux-2.4.0-test10 Marco d'Itri
2000-11-05 1:44 ` Linux-2.4.0-test10 H. Peter Anvin
2000-11-06 12:55 ` Linux-2.4.0-test10 Stephen C. Tweedie
2000-11-09 16:45 ` Linux-2.4.0-test10 Stephen C. Tweedie
2000-11-01 2:18 ` Tom Rini [this message]
2000-11-01 5:46 ` Linux-2.4.0-test10 Miles Lane
2000-11-01 5:43 ` Linux-2.4.0-test10 Linus Torvalds
2000-11-01 10:19 ` Linux-2.4.0-test10 Tigran Aivazian
2000-11-01 15:01 ` Linux-2.4.0-test10 Alan Cox
2000-11-01 15:19 ` Linux-2.4.0-test10 Tigran Aivazian
-- strict thread matches above, loose matches on Subject: below --
2000-11-01 6:03 Linux-2.4.0-test10 M.H.VanLeeuwen
2000-11-01 19:28 ` Linux-2.4.0-test10 David Ford
2000-11-02 0:08 ` Linux-2.4.0-test10 M.H.VanLeeuwen
2000-11-02 2:57 ` Linux-2.4.0-test10 David Ford
2000-11-02 7:15 ` Linux-2.4.0-test10 Vitezslav Samel
2000-11-01 12:51 Linux-2.4.0-test10 Mikael Pettersson
2000-11-01 16:12 Linux-2.4.0-test10 CRADOCK, Christopher
2000-11-02 0:44 ` Linux-2.4.0-test10 M.H.VanLeeuwen
2000-11-02 17:57 ` Linux-2.4.0-test10 Ragnar Hojland Espinosa
2000-11-02 18:38 ` Linux-2.4.0-test10 Ragnar Hojland Espinosa
2000-11-03 6:25 ` Linux-2.4.0-test10 kernel
2000-11-03 10:02 ` Linux-2.4.0-test10 Ben Ford
2000-11-07 10:22 ` Linux-2.4.0-test10 Ragnar Hojland Espinosa
2000-11-07 18:39 ` Linux-2.4.0-test10 Zephaniah E. Hull
2000-11-03 7:08 ` Linux-2.4.0-test10 James Simmons
2000-11-02 18:46 Linux-2.4.0-test10 CRADOCK, Christopher
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=20001031191807.A32641@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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