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:	Thu, 11 Jul 2013 16:19:45 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Yijing Wang <wangyijing@...wei.com>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, Rafael <rjw@...k.pl>,
	Hanjun Guo <guohanjun@...wei.com>, jiang.liu@...wei.com
Subject: Re: [PATCH -v2 0/3] Use PCIe DSN to improve pciehp_resume

On Thu, 2013-07-11 at 17:43 +0800, Yijing Wang wrote:
> v1->v2: Modify pci_get_dsn to pci_device_serial_number,
> 	    power off slot before remove the old device during resume to avoid
> 		old .remove() method to touch new hardware.
> 		Fix other typo and fail check problems.
> 		Split the list_empty() guard into new patch.
> 		
> 
> Yijing Wang (3):
>   PCI: introduce PCIe Device Serial Number Capability support
>   PCI,pciehp: avoid add a device already exist before suspend during
>     resume
>   PCI,pciehp: use PCIe DSN to identify device change during suspend
> 
>  drivers/pci/hotplug/pciehp_core.c |   54 ++++++++++++++++++++++++++++++++++--
>  drivers/pci/pci.c                 |   27 ++++++++++++++++++
>  drivers/pci/probe.c               |    2 +
>  include/linux/pci.h               |    3 ++
>  4 files changed, 83 insertions(+), 3 deletions(-)

Series applies cleanly to v3.10 (but there was a small problem with 3/3,
which I'll mention in a reply to that patch). Compiles without warning.
Those two errors on every resume are now gone!

Thanks.


Paul Bolle

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ