[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1330069619-14446-1-git-send-email-yinghai@kernel.org>
Date: Thu, 23 Feb 2012 23:46:48 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Yinghai Lu <yinghai@...nel.org>
Subject: [PATCH -v2 00/11] PCI: quirk related clean up
After commit:
| commit 3209874a1da2c51c7325e601d9634189ee178ad6
| Author: Arjan van de Ven <arjan@...radead.org>
| Date: Mon Jan 30 20:52:07 2012 -0800
|
| PCI: Annotate PCI quirks in initcall_debug style
will have lots of print out for quirks when initcall_debug is specified.
It turns out most of them are not really called for the devices because
quirks itself will check class id and bail out early.
Try to put class into quirk declaration. So we could avoid dive into these
quirks.
could be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci5
4ace9ad: PCI: Use class for quirk for usb host controller fixup
cc60c7c: PCI: Use class for quirk for ti816x class fixup
85fa49c: PCI: Use class for quirk for intel e100 interrupt fixup
8e4b35b: PCI: Use class for quirk for netmos class fixup
7c4b5d6: PCI: Use class for quirk for legacy ATA NO_D3
176e7df: PCI: Use class for quirk for cardbus_legacy
c2c7107: PCI: Use class for quirk for host bridge mmio_always_on
6924d3b: PCI: Use class for quirk for pci_fixup_video
7133c84: PCI: Use class quirk for intel fix_transparent_bridge
bf9f6e6: PCI: Use class for quirk for via_no_dac
d2e6e88: PCI: Add class support in quirk handling
-v2: separate to small patches for different quirk according to Jesse.
Thanks
Yinghai
arch/x86/kernel/pci-dma.c | 5 ++-
arch/x86/pci/fixup.c | 12 +++----
drivers/pci/quirks.c | 61 +++++++++++++++++++++------------------
drivers/usb/host/pci-quirks.c | 3 +-
include/linux/pci.h | 63 +++++++++++++++++++++++++++++++++-------
5 files changed, 95 insertions(+), 49 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists