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 2.6.27
Date: Wed, 15 Oct 2008 23:44:53 +0200 (CEST) [thread overview]
Message-ID: <tkrat.6559742adfdec1ce@s5r6.in-berlin.de> (raw)
Linus, please pull from the for-linus branch at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git for-linus
to receive the following IEEE 1394/ FireWire subsystem updates.
We have got little fixes, the last small bit of BKL removal in the old
stack, and further improved connection stability in the old stack. Some
work on the new stack has been going on too, but too slow to make it for
this merge.
Jay Fenlason (2):
firewire: fw_send_request_sync()
firewire: Add more documentation to firewire-cdev.h
Julia Lawall (1):
ieee1394: Use DIV_ROUND_UP
Stefan Richter (13):
ieee1394: sbp2: stricter dma_sync
ieee1394: sbp2: check for DMA mapping failures
ieee1394: sbp2: enforce s/g segment size limit
ieee1394: raw1394: replace BKL by local mutex, make ioctl() and mmap() thread-safe
ieee1394: raw1394: narrow down the state_mutex protected region
ieee1394: raw1394: make write() thread-safe
ieee1394: dv1394, video1394: remove unnecessary expressions
ieee1394: nodemgr clean up class iterators
ieee1394: survive a few seconds connection loss
firewire: fw-sbp2: enforce s/g segment size limit
firewire: fw-sbp2: fix another small generation access bug
firewire: fix setting tag and sy in iso transmission
firewire: fix ioctl() return code
drivers/firewire/fw-card.c | 56 ++----
drivers/firewire/fw-cdev.c | 6 +-
drivers/firewire/fw-device.c | 37 +---
drivers/firewire/fw-sbp2.c | 116 +++++-------
drivers/firewire/fw-transaction.c | 48 +++++-
drivers/firewire/fw-transaction.h | 9 +-
drivers/ieee1394/csr1212.c | 2 +-
drivers/ieee1394/dv1394.c | 2 +-
drivers/ieee1394/eth1394.c | 2 +-
drivers/ieee1394/nodemgr.c | 279 +++++++++++-----------------
drivers/ieee1394/nodemgr.h | 2 +-
drivers/ieee1394/raw1394-private.h | 1 +
drivers/ieee1394/raw1394.c | 230 +++++++++++++----------
drivers/ieee1394/sbp2.c | 218 +++++++++-------------
drivers/ieee1394/sbp2.h | 33 +---
drivers/ieee1394/video1394.c | 8 +-
include/linux/firewire-cdev.h | 9 +-
17 files changed, 470 insertions(+), 588 deletions(-)
Thanks,
--
Stefan Richter
-=====-==--- =-=- -====
http://arcgraph.de/sr/
reply other threads:[~2008-10-15 21:45 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=tkrat.6559742adfdec1ce@s5r6.in-berlin.de \
--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
all inboxes | Powered by JetHome®