linux-kernel - [git pull] FireWire updates post v3.6

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

Message-ID: <20121003194731.226dd535@stein>
Date:	Wed, 3 Oct 2012 19:47:31 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux1394-devel@...ts.sourceforge.net
Subject: [git pull] FireWire updates post v3.6

Linus,

please pull from the tag "firewire-updates" at

    git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git firewire-updates

to receive the following IEEE 1394 (FireWire) subsystem changes:
  - Feed GUIDs of FireWire nodes to the random pool,
  - more complete quirk handling of a TI S400B phy,
  - avoid holding a core lock while calling into highlevel drivers.
Thanks.

Clemens Ladisch (1):
      firewire: core: feed /dev/random with devices' GUIDs

Peter Hurley (1):
      firewire: remove global lock around address handlers, convert to RCU

Stefan Richter (1):
      firewire: addendum to address handler RCU conversion

Stephan Gatzka (1):
      firewire: ohci: get IR bit from TSB41BA3D phy

 drivers/firewire/core-device.c      |  3 +++
 drivers/firewire/core-transaction.c | 33 +++++++++++++++++++--------------
 drivers/firewire/ohci.c             | 28 +++++++++++++++++++++++++++-
 include/linux/firewire.h            | 12 ++++++++++--
 4 files changed, 59 insertions(+), 17 deletions(-)
-- 
Stefan Richter
-=====-===-- =-=- ---==
http://arcgraph.de/sr/
--
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/