linux-kernel - [git pull] FireWire (IEEE 1394) updates post v3.18

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: <20141215184231.5b006cab@kant>
Date:	Mon, 15 Dec 2014 18:42:31 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux1394-devel@...ts.sourceforge.net
Subject: [git pull] FireWire (IEEE 1394) updates post v3.18

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 subsystem updates:
Clean up firewire-ohci's longlived vm-mapping;
use target instance lock instead of core lock in firewire-sbp2.

Clemens Ladisch (1):
      firewire: ohci: replace vm_map_ram() with vmap()

Stefan Richter (4):
      firewire: core: document fw_csr_string's truncation of long strings
      firewire: sbp2: protect a reference counter properly
      firewire: sbp2: replace some spin_lock_irqsave by spin_lock_irq
      firewire: sbp2: replace card lock by target lock

 drivers/firewire/core-device.c |  3 +++
 drivers/firewire/ohci.c        |  6 ++----
 drivers/firewire/sbp2.c        | 67 ++++++++++++++++++++++++++++++-------------------------------------
 3 files changed, 35 insertions(+), 41 deletions(-)

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