linux-kernel - [PATCH v2 0/7] pci/e1000e: return runtime-pm back to work

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-next>] [day] [month] [year] [list]

Message-ID: <20130204115246.5569.85829.stgit@zurg>
Date:	Mon, 04 Feb 2013 15:55:47 +0400
From:	Konstantin Khlebnikov <khlebnikov@...nvz.org>
To:	e1000-devel@...ts.sourceforge.net, linux-pci@...r.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/7] pci/e1000e: return runtime-pm back to work

This patchset contains some fixes for e1000e diver (broken since v2.6.35)
and some related fixes and useful debug for PCI code.

All together this fixes my regression report for v3.8-rc1:
https://lkml.org/lkml/2013/1/1/25

patchset was seriously reworked since v1:
http://lkml.org/lkml/2013/1/18/147

---

Konstantin Khlebnikov (6):
      e1000e: fix pci-device enable-counter balance
      PCI: don't touch enable_cnt in pci_device_shutdown()
      PCI: catch enable-counter underflows
      e1000e: fix runtime power management transitions
      PCI/PM: warn about incomplete actions in ->runtime_suspend() callback
      e1000e: fix accessing to suspended device

Rafael J. Wysocki (1):
      PCI/PM: clear state_saved during suspend


 drivers/net/ethernet/intel/e1000e/ethtool.c |   13 ++++
 drivers/net/ethernet/intel/e1000e/netdev.c  |   82 +++++++--------------------
 drivers/pci/pci-driver.c                    |   21 +++++--
 drivers/pci/pci.c                           |    3 +
 4 files changed, 53 insertions(+), 66 deletions(-)

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