From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: [GIT PATCH] PCI fixes for 2.6.17-rc3
Date: Thu, 27 Apr 2006 13:16:17 -0700 [thread overview]
Message-ID: <20060427201617.GC2101@kroah.com> (raw)
Here are some small PCI fixes against your latest git tree. They have
all been in the -mm tree for a while with no problems.
Please pull from:
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/pci-2.6.git/
or if master.kernel.org hasn't synced up yet:
master.kernel.org:/pub/scm/linux/kernel/git/gregkh/pci-2.6.git/
The full patches will be sent to the linux-pci mailing list, if anyone
wants to see them.
thanks,
greg k-h
Documentation/pci.txt | 12 +++++++++++-
arch/i386/pci/irq.c | 1 -
drivers/pci/msi.c | 4 +++-
drivers/pci/quirks.c | 6 ++++--
4 files changed, 18 insertions(+), 5 deletions(-)
---------------
Chris Wedgwood:
PCI quirk: VIA IRQ fixup should only run for VIA southbridges
Greg Kroah-Hartman:
PCI: fix via irq SATA patch
Ingo Oeser:
PCI: Documentation: no more device ids
Jesper Juhl:
PCI: fix potential resource leak in drivers/pci/msi.c
reply other threads:[~2006-04-27 20:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060427201617.GC2101@kroah.com \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--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
Powered by JetHome