From: Alexandre Buisse <alexandre.buisse@ens-lyon.fr>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.13
Date: Wed, 31 Aug 2005 14:42:45 +0200 [thread overview]
Message-ID: <4315A5C5.6080903@ens-lyon.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0508281708040.3243@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
Hi,
the description of PCI_NAMES is conflicting with its default option (now
N/y/? instead of Y/n/?). Here is a small patch that should remove the
confusion in drivers/pci/Kconfig.
Regards,
Alexandre
Signed-off-by : Alexandre Buisse <Alexandre.Buisse@ens-lyon.fr>
[-- Attachment #2: pci_names_desc_update.patch --]
[-- Type: text/x-patch, Size: 714 bytes --]
--- drivers/pci/Kconfig.old 2005-08-31 14:35:06.000000000 +0200
+++ drivers/pci/Kconfig 2005-08-31 14:35:14.000000000 +0200
@@ -34,7 +34,7 @@
bool "PCI device name database"
depends on PCI
---help---
- By default, the kernel contains a database of all known PCI device
+ The kernel can contain a database of all known PCI device
names to make the information in /proc/pci, /proc/ioports and
similar files comprehensible to the user.
@@ -45,7 +45,7 @@
embedded system where kernel image size really matters, you can disable
this feature and you'll get device ID numbers instead of names.
- When in doubt, say Y.
+ When in doubt, say N.
config PCI_DEBUG
bool "PCI Debugging"
next prev parent reply other threads:[~2005-08-31 13:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 0:17 Linux 2.6.13 Linus Torvalds
2005-08-29 0:43 ` Jesper Juhl
2005-08-29 3:05 ` Linus Torvalds
2005-08-29 10:57 ` Steven Rostedt
2005-08-29 12:17 ` Nigel Cunningham
2005-08-29 12:25 ` Jörn Engel
2005-08-29 12:28 ` Nigel Cunningham
2005-08-29 14:25 ` Antonino A. Daplas
2005-08-29 14:42 ` Steven Rostedt
2005-08-29 14:50 ` Linus Torvalds
2005-08-29 15:44 ` [PATCH] convert signal handling of NODEFER to act like other Unix boxes Steven Rostedt
2005-08-29 18:04 ` [PATCH] convert signal handling of NODEFER to act like other Unix boxes. [take2] Steven Rostedt
2005-08-29 12:19 ` Linux 2.6.13 Nigel Cunningham
2005-08-29 14:22 ` Roland Dreier
2005-09-01 6:24 ` reboot vs poweroff (was: Linux 2.6.13) Meelis Roos
2005-09-01 6:48 ` Nigel Cunningham
2005-09-01 7:33 ` Meelis Roos
2005-09-01 12:32 ` Pierre Ossman
2005-09-01 12:48 ` Nigel Cunningham
2005-09-01 15:15 ` Eric W. Biederman
2005-09-01 15:19 ` reboot vs poweroff Pierre Ossman
2005-09-01 17:00 ` Eric W. Biederman
2005-09-01 18:19 ` Pierre Ossman
2005-09-01 18:23 ` Eric W. Biederman
2005-09-01 21:11 ` Nigel Cunningham
2005-09-02 4:46 ` Eric W. Biederman
2005-09-01 20:22 ` Pavel Machek
2005-09-02 4:26 ` Eric W. Biederman
2005-09-01 21:09 ` reboot vs poweroff (was: Linux 2.6.13) Nigel Cunningham
2005-08-29 18:23 ` Oops in 2.6.13 (was Linux 2.6.13 ) Masoud Sharbiani
2005-08-29 20:13 ` Lee Revell
2005-08-30 3:47 ` Masoud Sharbiani
2005-08-30 22:41 ` Linux 2.6.13 Henrik Persson
2005-09-01 2:29 ` Greg KH
2005-09-03 9:22 ` Henrik Persson
2005-08-31 12:42 ` Alexandre Buisse [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-29 2:34 Jerome Pinot
2005-08-29 3:27 ` Linus Torvalds
2005-08-29 23:57 Ricardo Galli
2005-09-03 16:16 ` Alexey Dobriyan
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=4315A5C5.6080903@ens-lyon.fr \
--to=alexandre.buisse@ens-lyon.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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