public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>, greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: [2.4 patch] hotplug: add missing Configure.help entries
Date: Wed, 19 May 2004 20:14:41 +0200	[thread overview]
Message-ID: <20040519181441.GI22742@fs.tum.de> (raw)
In-Reply-To: <20040503230911.GE7068@logos.cnet>

On Mon, May 03, 2004 at 08:09:12PM -0300, Marcelo Tosatti wrote:
>...
> Summary of changes from v2.4.27-pre1 to v2.4.27-pre2
> ============================================
>...
> Dely Sy:
>   o SHPC and PCI Express hot-plug drivers for 2.4 kernel
>...

People seem to tend to forget Configure.help entries for new drivers...

Below is a patch to add Configure.help entries based on the entries 
in 2.6 .

Please apply
Adrian

--- linux-2.4.27-pre3-full/Documentation/Configure.help.old	2004-05-19 20:04:49.000000000 +0200
+++ linux-2.4.27-pre3-full/Documentation/Configure.help	2004-05-19 20:10:22.000000000 +0200
@@ -4300,6 +4300,26 @@
   The module will be called acpiphp.o. If you want to compile it
   as a module, say M here and read <file:Documentation/modules.txt>.
 
+CONFIG_HOTPLUG_PCI_SHPC
+  Say Y here if you have a motherboard with a SHPC PCI Hotplug
+  controller.
+
+CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE
+  Say Y here if you want to use the polling mechanism for hot-plug 
+  events for early platform testing.
+
+CONFIG_HOTPLUG_PCI_SHPC_PHPRM_LEGACY
+  Say Y here for AMD SHPC. You have to select this option if you are 
+  using this driver on platform with AMD SHPC.
+
+CONFIG_HOTPLUG_PCI_PCIE
+  Say Y here if you have a motherboard that supports PCI Express Native
+  Hotplug
+
+CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE
+  Say Y here if you want to use the polling mechanism for hot-plug 
+  events for early platform testing.
+
 MCA support
 CONFIG_MCA
   MicroChannel Architecture is found in some IBM PS/2 machines and

      parent reply	other threads:[~2004-05-22  0:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 23:09 Linux 2.4.27-pre2 Marcelo Tosatti
2004-05-04  3:49 ` Frédéric L. W. Meunier
2004-05-04 19:19 ` Linux 2.4.27-pre2 (gcc-3.4.0) Rafał 'rmrmg' Roszak
     [not found]   ` <200405042146.40404@WOLK>
2004-05-04 20:03     ` Rafał 'rmrmg' Roszak
2004-05-05  6:36       ` Rene Rebe
2004-05-05  8:15         ` Rafał 'rmrmg' Roszak
2004-05-05  9:30           ` Mikael Pettersson
2004-05-05  9:53             ` Rene Rebe
2004-05-05 10:20               ` Mikael Pettersson
2004-05-04 20:46 ` 2.4.27-pre2: tg3: there's no WARN_ON in 2.4 Adrian Bunk
2004-05-04 20:53   ` Marc-Christian Petersen
2004-05-04 20:56     ` Jeff Garzik
2004-05-05  3:18       ` David S. Miller
2004-05-05  8:57         ` Marc-Christian Petersen
2004-05-05 19:30           ` David S. Miller
2004-05-04 23:44     ` Eyal Lebedinsky
2004-05-06 12:13       ` Adrian Bunk
2004-05-12  0:07         ` H. Peter Anvin
2004-05-13 22:34           ` Adrian Bunk
2004-05-13 23:03             ` H. Peter Anvin
2004-05-17  0:38               ` Adrian Bunk
2004-05-05 23:50 ` Linux 2.4.27-pre2 Eyal Lebedinsky
2004-05-07 13:49   ` Marcelo Tosatti
2004-05-19 18:14 ` Adrian Bunk [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=20040519181441.GI22742@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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