From: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
To: <bunk@stusta.de>
Cc: <greg@kroah.com>, <linux-kernel@vger.kernel.org>,
"Nguyen, Tom L" <tom.l.nguyen@intel.com>,
"Roland Dreier" <roland@topspin.com>
Subject: RE: [2.6 patch] PCI cleanups
Date: Mon, 15 Nov 2004 11:41:10 -0800 [thread overview]
Message-ID: <C7AB9DA4D0B1F344BF2489FA165E502406F1D41C@orsmsx404.amr.corp.intel.com> (raw)
On Friday, November 12, 2004 7:02 PM Adrian Bunk wrote:
> The patch below does some cleanups in the PCI code:
> - make OSC_UUID in drivers/pci/pci-acpi.c static
> - remove the completely unused drivers/pci/hotplug/pciehp_sysfs.c
> - remove other unused code
Your patch mistakenly removes PCI MSI-X support in the kernel. Please
do not remove PCI MSI-X support code.
Thanks,
Long
next reply other threads:[~2004-11-15 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 19:41 Nguyen, Tom L [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-13 3:02 [2.6 patch] PCI cleanups Adrian Bunk
2004-11-15 19:51 ` Greg KH
2004-11-15 20:30 ` Roland Dreier
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=C7AB9DA4D0B1F344BF2489FA165E502406F1D41C@orsmsx404.amr.corp.intel.com \
--to=tom.l.nguyen@intel.com \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.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;
as well as URLs for NNTP newsgroup(s).