public inbox for linux-kernel@vger.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.10
Date: Sun, 7 Jul 2013 10:49:25 +0200	[thread overview]
Message-ID: <20130707104925.5e1fcf5b@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 struct ieee1394_device_id.driver_data actually avaliable to
1394 protocol drivers.  This is especially useful to 1394 audio drivers
for model-specific parameters and methods.

Stefan Richter (2):
      firewire: introduce fw_driver.probe and .remove methods
      firewire: remove support of fw_driver.driver.probe and .remove methods

 drivers/firewire/core-device.c      |  39 +++++++++++++++-----
 drivers/firewire/net.c              |  50 +++++++++++++-------------
 drivers/firewire/sbp2.c             |  17 ++++-----
 drivers/media/firewire/firedtv-fw.c |  19 +++++-----
 drivers/staging/fwserial/fwserial.c |  14 ++++----
 include/linux/firewire.h            |   2 ++
 sound/firewire/isight.c             |  44 +++++++++++------------
 sound/firewire/scs1x.c              |  39 ++++++++++----------
 sound/firewire/speakers.c           | 106 ++++++++++++++++++++++---------------------------------
 9 files changed, 160 insertions(+), 170 deletions(-)

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

                 reply	other threads:[~2013-07-07  8:49 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=20130707104925.5e1fcf5b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox