From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI fixes for 2.6.4-rc1
Date: Fri, 27 Feb 2004 16:09:44 -0800 [thread overview]
Message-ID: <10779269841823@kroah.com> (raw)
In-Reply-To: <1077926983983@kroah.com>
ChangeSet 1.1619, 2004/02/24 14:04:40-08:00, greg@kroah.com
PCI Hotplug: clean up the Makefile a bit more.
Still need to fix up the pcie and shpc options to be saner for distros to use.
drivers/pci/hotplug/Makefile | 18 ++++++++----------
1 files changed, 8 insertions(+), 10 deletions(-)
diff -Nru a/drivers/pci/hotplug/Makefile b/drivers/pci/hotplug/Makefile
--- a/drivers/pci/hotplug/Makefile Fri Feb 27 15:57:08 2004
+++ b/drivers/pci/hotplug/Makefile Fri Feb 27 15:57:08 2004
@@ -25,6 +25,8 @@
cpqphp_ctrl.o \
cpqphp_sysfs.o \
cpqphp_pci.o
+cpqphp-$(CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM) += cpqphp_nvram.o
+cpqphp-objs += $(cpqphp-y)
ibmphp-objs := ibmphp_core.o \
ibmphp_ebda.o \
@@ -49,21 +51,17 @@
pciehp_sysfs.o \
pciehp_hpc.o
-shpchp-objs := shpchp_core.o \
- shpchp_ctrl.o \
- shpchp_pci.o \
- shpchp_sysfs.o \
- shpchp_hpc.o
-
-ifeq ($(CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM),y)
- cpqphp-objs += cpqphp_nvram.o
-endif
-
ifeq ($(CONFIG_HOTPLUG_PCI_PCIE_PHPRM_NONACPI),y)
pciehp-objs += pciehprm_nonacpi.o
else
pciehp-objs += pciehprm_acpi.o
endif
+
+shpchp-objs := shpchp_core.o \
+ shpchp_ctrl.o \
+ shpchp_pci.o \
+ shpchp_sysfs.o \
+ shpchp_hpc.o
ifeq ($(CONFIG_HOTPLUG_PCI_SHPC_PHPRM_LEGACY),y)
shpchp-objs += shpchprm_legacy.o
prev parent reply other threads:[~2004-02-28 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 0:07 [BK PATCH] PCI fixes for 2.6.4-rc1 Greg KH
2004-02-28 0:09 ` [PATCH] " Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` Greg KH [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=10779269841823@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@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 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.