From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: [git pull] FireWire updates post v3.4
Date: Thu, 24 May 2012 21:14:55 +0200 [thread overview]
Message-ID: <20120524211455.6c3464cd@stein> (raw)
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 updates:
- Fix mismatch between DMA mapping direction (was wrong) and DMA synchronization
direction (was correct) of isochronous reception buffers of userspace drivers
if vma-mapped for R/W access. For example, libdc1394 was affected.
- more consistent retry stategy in device discovery/ rediscovery, and improved
failure diagnostics
- various small cleanups, e.g. use SCSI layer's DMA mapping API in firewire-sbp2
The last few commits happened rather late for this pull request but I feel comfortable
with them. ALSA firewire-lib changes were written by Clemens, hence are implicitly ACKed.
Axel Lin (1):
firewire: use module_pci_driver
Clemens Ladisch (10):
firewire: core: wait for inaccessible devices after bus reset
firewire: core: improve reread_config_rom() interface
firewire: move rcode_string() to core
firewire: core: log error in case of failed bus manager lock
firewire: core: log config rom reading errors
firewire: core: fw_device_refresh(): clean up error handling
firewire: sbp2: give correct DMA device to scsi framework
firewire: sbp2: use scsi_dma_(un)map
firewire: sbp2: remove superfluous blk_queue_max_segment_size() call
firewire: sbp2: document the absence of alignment requirements
Stefan Richter (4):
firewire: core: fix DMA mapping direction
firewire: ohci: correct signedness of a local variable
firewire: ohci: omit spinlock IRQ flags where possible
Merge tag 'v3.4' with SCSI updates, needed for subsequent firewire-sbp2 changes
drivers/firewire/core-card.c | 4 +-
drivers/firewire/core-cdev.c | 51 ++++++++++++---
drivers/firewire/core-device.c | 116 +++++++++++++++++------------------
drivers/firewire/core-iso.c | 80 +++++++++++++++---------
drivers/firewire/core-transaction.c | 26 ++++++++
drivers/firewire/core.h | 7 ++-
drivers/firewire/nosy.c | 20 ++----
drivers/firewire/ohci.c | 42 +++++--------
drivers/firewire/sbp2.c | 28 ++++-----
include/linux/firewire.h | 2 +
sound/firewire/cmp.c | 2 +-
sound/firewire/lib.c | 28 +--------
sound/firewire/lib.h | 1 -
13 files changed, 218 insertions(+), 189 deletions(-)
Thanks,
--
Stefan Richter
-=====-===-- -=-= ==---
http://arcgraph.de/sr/
reply other threads:[~2012-05-24 19:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120524211455.6c3464cd@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox