All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: [git pull] FireWire updates post v3.13
Date: Mon, 27 Jan 2014 15:01:25 +0100	[thread overview]
Message-ID: <20140127150125.4c9bb5f5@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 changes:

  - make remote debugging over 1394 a runtime option instead of a
    buildtime option

  - extend remote debug access past the 4 GB barrier on respectively
    capable hardware

  - documentation update

The cross-tree changes in lib/ and in Documentation/ do not conflict with
anything else in linux-next AFAIK.


Lubomir Rintel (2):
      Documentation/: update FireWire debugging documentation
      firewire: ohci: Turn remote DMA support into a module parameter

Stefan Richter (1):
      firewire: Enable remote DMA above 4 GB

 Documentation/debugging-via-ohci1394.txt   | 41 +++++++++++++++++++----------------------
 Documentation/power/basic-pm-debugging.txt |  2 +-
 drivers/firewire/core-transaction.c        |  6 +++---
 drivers/firewire/core.h                    |  3 +++
 drivers/firewire/ohci.c                    | 27 ++++++++++++++++-----------
 lib/Kconfig.debug                          | 11 -----------
 6 files changed, 42 insertions(+), 48 deletions(-)

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

                 reply	other threads:[~2014-01-27 14:01 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=20140127150125.4c9bb5f5@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --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.