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.37
Date: Fri, 7 Jan 2011 17:55:39 +0100 [thread overview]
Message-ID: <20110107175539.2b882d3d@stein> (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 updates for the IEEE 1394 (FireWire) subsystem.
Most importantly this improves reception of asynchronous block packets
with larger payload (outside physical DMA), as used by IP over 1394 or
for example forensics applications.
As not all patches had been crossposted to lkml yet, I will send the
full log and diff as reply to this mail.
Clemens Ladisch (10):
firewire: ohci: Asynchronous Reception rewrite
firewire: ohci: fix AT context initialization error handling
firewire: ohci: flush MMIO writes in the interrupt handler
firewire: ohci: properly clear posted write errors
firewire: make PHY packet header format consistent
firewire: ohci: optimize iso context checks in the interrupt handler
firewire: ohci: use common buffer for self IDs and AR descriptors
firewire: ohci: flush AT contexts after bus reset for OHCI 1.2
firewire: ohci: cache the context run bit
firewire: use split transaction timeout only for split transactions
Joe Perches (1):
firewire: core: Update WARN uses
Maxim Levitsky (4):
firewire: ohci: restore GUID on resume.
firewire: ohci: restart iso DMA contexts on resume from low power mode
firewire: net: ratelimit error messages
firewire: net: add carrier detection
Stefan Richter (4):
firewire: nosy: char device is not seekable
firewire: net: set carrier state at ifup
firewire: ohci: flush AT contexts after bus reset - addendum
firewire: ohci: consolidate context status flags
drivers/firewire/Kconfig | 2 +-
drivers/firewire/core-cdev.c | 7 +-
drivers/firewire/core-transaction.c | 58 ++-
drivers/firewire/core.h | 4 +-
drivers/firewire/net.c | 47 ++-
drivers/firewire/nosy.c | 3 +-
drivers/firewire/ohci.c | 672 ++++++++++++++++++++++++-----------
include/linux/firewire.h | 2 +-
8 files changed, 548 insertions(+), 247 deletions(-)
Thanks,
--
Stefan Richter
-=====-==-== ---= --===
http://arcgraph.de/sr/
next reply other threads:[~2011-01-07 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 16:55 Stefan Richter [this message]
2011-01-07 16:56 ` [git pull] FireWire updates post 2.6.37 Stefan Richter
2011-01-13 15:00 ` [git pull] FireWire build fix 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=20110107175539.2b882d3d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.