mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.30, the rest
Date: Mon, 22 Jun 2009 17:43:16 +0200 (CEST)	[thread overview]
Message-ID: <tkrat.190a88350b3d25c7@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.9282749343d60f9f@s5r6.in-berlin.de>

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.
The shortlog says it all --- drivers/firewire gains IPv4 support and is
no longer considered experimental.

The "new" firewire stack is now preferable over the older ieee1394 stack
*except for audio devices* (FireWire audio devices for sound studios,
driven by the FFADO + Jack userspace framework), and for FireWire DVB
boxes driven by the firedtv kernel driver (to be adapted to the new
firewire stack RSN).  Distributors who like to utilize the enhanced
features, performance, and security of the new stack but also want to
support pro/ semi-pro FireWire audio and FireWire DVB too can easily
package both the old and the new stack.  Some more info is provided via
the Kconfig help text.

The code in this form has been in linux-next for merely a week, even
though the bulk of it was supplied to linux1394-devel in May.  Sorry for
my being slow to line it up.

Jay Fenlason (1):
      firewire: add IPv4 support

Stefan Richter (10):
      firewire: net: add Kconfig item, rename driver
      firewire: net: style changes
      firewire: net: allow for unordered unit discovery
      firewire: net: remove unused code
      firewire: net: adjust net_device ops
      firewire: core: fix DMA unmapping in iso buffer removal
      firewire: core: fix iso context shutdown on card removal
      firewire: net: fix card driver reloading
      firewire: net: better FIFO address range check and rcodes
      firewire: new stack is no longer experimental

 drivers/firewire/Kconfig     |   60 +-
 drivers/firewire/Makefile    |    4 +-
 drivers/firewire/core-card.c |   20 +-
 drivers/firewire/core-iso.c  |   11 +-
 drivers/firewire/core.h      |   87 ---
 drivers/firewire/net.c       | 1655 ++++++++++++++++++++++++++++++++++++++++++
 drivers/ieee1394/Kconfig     |   19 +-
 include/linux/firewire.h     |   87 +++
 8 files changed, 1807 insertions(+), 136 deletions(-)
 create mode 100644 drivers/firewire/net.c

Thanks,
-- 
Stefan Richter
-=====-==--= -==- =-==-
http://arcgraph.de/sr/


      reply	other threads:[~2009-06-22 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 21:22 [git pull] FireWire updates post 2.6.30 Stefan Richter
2009-06-22 15:43 ` Stefan Richter [this message]

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.190a88350b3d25c7@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®