linux-kernel - Re: [git pull] PCI changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 29 Oct 2011 01:30:44 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [git pull] PCI changes

Hi,

On Friday, October 28, 2011, Jesse Barnes wrote:
> Note!  There are two branches available, see below.
> 
> The following changes since commit
> e9308cfd5ab4ade3d81cf591c7599c3a05a21b04:
> 
>   Merge branch 'gpio/merge' of git://git.secretlab.ca/git/linux-2.6 (2011-10-14 17:07:52 +1200)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci next-revert
> 
> Probably the most exciting bits of this series are the MPS fixes and
> Joerg's PASID stuff.  But I don't think there's anything really risky
> (i.e. no big resource management changes this time around).
> 
> We found a problem on PPC with the latency setup changes, so this
> branch includes reverts for those patches.  However, another branch is
> available with those patches rebased out if you prefer a cleaner
> changelog.  See below for the changelog and diffstat to expect from
> that branch.
> 
> Ben Hutchings (2):
>       PCI: Add Solarflare vendor ID and SFC4000 device IDs
>       PCI: Add quirk for known incorrect MPSS
> 
> Benjamin Herrenschmidt (2):
>       PCI: Make pci_setup_bridge() non-static for use by arch code
>       pci: Clamp pcie_set_readrq() when using "performance" settings
> 
> Jan Beulich (1):
>       x86: constify PCI raw ops structures
> 
> Jesse Barnes (7):
>       Revert "PCI: latency timer doesn't apply to PCIe"
>       Revert "PCI: x86: use generic pcibios_set_master()"
>       Revert "PCI: sh: use generic pcibios_set_master()"
>       Revert "PCI: mn10300: use generic pcibios_set_master()"
>       Revert "PCI: mips: use generic pcibios_set_master()"
>       Revert "PCI: frv: use generic pcibios_set_master()"
>       Revert "PCI: Pull PCI 'latency timer' setup up into the core"
> 
> Joerg Roedel (4):
>       PCI: Move ATS implementation into own file
>       PCI: Export ATS functions to modules
>       PCI: Add implementation for PRI capability
>       PCI: Add support for PASID capability
> 
> Jon Mason (3):
>       PCI: Workaround for Intel MPS errata
>       PCI: enable MPS "performance" setting to properly handle bridge MPS
>       PCI: Clean-up MPS debug output
> 
> Josh Boyer (1):
>       PCI quirk: mmc: Always check for lower base frequency quirk for Ricoh 1180:e823
> 
> Myron Stowe (7):
>       PCI: Pull PCI 'latency timer' setup up into the core
>       PCI: frv: use generic pcibios_set_master()
>       PCI: mips: use generic pcibios_set_master()
>       PCI: mn10300: use generic pcibios_set_master()
>       PCI: sh: use generic pcibios_set_master()
>       PCI: x86: use generic pcibios_set_master()
>       PCI: latency timer doesn't apply to PCIe
> 
> Prarit Bhargava (1):
>       PCI hotplug: acpiphp: Prevent deadlock on PCI-to-PCI bridge remove
> 
> Rafael J. Wysocki (2):
>       PCI / PM: Extend PME polling to all PCI devices
>       PCI / PM: Remove unnecessary error variable from acpi_dev_run_wake()

Any chance to push https://lkml.org/lkml/2011/10/21/192 any time soon?

It pretty much is a necessary fix for a problem with _OSC after some
recent changes.

Thanks,
Rafael
--
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/