From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: [GIT PULL] FireWire updates post 2.6.23
Date: Wed, 17 Oct 2007 00:39:10 +0200 (CEST) [thread overview]
Message-ID: <tkrat.762cf4d84dd2db77@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. It's
almost all just bugfixes, and had I anticipated that 2.6.23 was going to
grow an -rc9 I would have sent most of the material for the new firewire
stack already during the rc phase.
Most patches went into -mm during mid July...mid September; some simple
patches are from the past two weeks. Combined diff follows in a reply.
Stat and shortlog:
drivers/firewire/fw-cdev.c | 52 ++-
drivers/firewire/fw-device.h | 5 -
drivers/firewire/fw-ohci.c | 41 ++-
drivers/firewire/fw-ohci.h | 2 +
drivers/firewire/fw-sbp2.c | 647 +++++++++++++++++------------
drivers/firewire/fw-topology.c | 10 +-
drivers/firewire/fw-topology.h | 6 -
drivers/firewire/fw-transaction.c | 12 +-
drivers/ieee1394/csr1212.c | 57 ++--
drivers/ieee1394/csr1212.h | 6 +-
drivers/ieee1394/eth1394.c | 16 +-
drivers/ieee1394/ieee1394_core.c | 2 +-
drivers/ieee1394/nodemgr.c | 22 +-
drivers/ieee1394/pcilynx.c | 29 +-
drivers/ieee1394/sbp2.c | 15 +
include/linux/firewire-cdev.h | 15 +
16 files changed, 560 insertions(+), 377 deletions(-)
Jay Fenlason (1):
firewire: fw-cdev: reorder wakeup vs. spinlock
Jean Delvare (1):
ieee1394: pcilynx: I2C cleanups
Matthias Kaehlcke (1):
ieee1394: ieee1394_core.c: use DEFINE_SPINLOCK for spinlock definition
Satyam Sharma (1):
ieee1394: Fix kthread stopping in nodemgr_host_thread
Stefan Richter (20):
ieee1394: eth1394: superfluous local variable
ieee1394: eth1394: fix lock imbalance
ieee1394: pcilynx: superfluous local variables
ieee1394: sbp2: fix unsafe iteration over list of devices
ieee1394: nodemgr: fix leak of struct csr1212_keyval
ieee1394: csr1212: proper refcounting
firewire: optimize fw_core_add_address_handler
firewire: fw-core: local variable shadows a global one
firewire: fw-sbp2: always enable IRQs before calling command ORB callback
firewire: fw-sbp2: add support for multiple logical units per target
firewire: fw-sbp2: expose module parameter for workarounds
firewire: fw-sbp2: use an own workqueue (fix system responsiveness)
firewire: fw-ohci: enforce read order for selfID generation
firewire: fw-ohci: fix includes
firewire: fw-ohci: reorder includes
firewire: fw-ohci: log posted write errors
firewire: fw-ohci: missing dma_unmap_single
firewire: fw-ohci: check for misconfigured bus (phyID == 63)
firewire: adopt read cycle timer ABI from raw1394
firewire: a header cleanup
Yann Dirson (1):
firewire: in-code doc updates.
--
Stefan Richter
-=====-=-=== =-=- =---=
http://arcgraph.de/sr/
next reply other threads:[~2007-10-16 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 22:39 Stefan Richter [this message]
2007-10-16 22:40 ` Stefan Richter
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.762cf4d84dd2db77@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®