From: Clemens Ladisch <clemens@ladisch.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
linux1394-devel@lists.sourceforge.net,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Peter Hurley <peter@hurleysoftware.com>
Subject: Re: [PATCH] firewire: introduce fw_driver.probe and .remove methods
Date: Mon, 03 Jun 2013 09:17:28 +0200 [thread overview]
Message-ID: <51AC4308.2030200@ladisch.de> (raw)
In-Reply-To: <20130603002749.4fdc36a5@stein>
Stefan Richter wrote:
> FireWire upper layer drivers are converted from generic
> struct driver.probe() and .remove()
> to bus-specific
> struct fw_driver.probe() and .remove().
Acked-by: Clemens Ladisch <clemens@ladisch.de>
for these:
> sound/firewire/isight.c | 44 ++++++------
> sound/firewire/scs1x.c | 39 +++++-----
> sound/firewire/speakers.c | 106 +++++++++++-----------------
> Although all in-tree drivers are being converted to the new methods,
> support for the old methods is left in place for the time being, aiming
> to avoid conflicts if/when new drivers are being merged into the
> mainline via other trees.
AFAICS it's unlikely that any of the new sound drivers will be merged soon
enough for this to matter.
Regards,
Clemens
prev parent reply other threads:[~2013-06-03 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51A20AEE.7060201@sakamocchi.jp>
2013-05-26 21:35 ` How to get driver_data of struct ieee1394_device_id in kernel driver module? Stefan Richter
2013-05-26 22:15 ` Stefan Richter
2013-05-26 22:57 ` Greg Kroah-Hartman
2013-05-29 18:09 ` Stefan Richter
2013-05-30 12:14 ` Takashi Sakamoto
2013-06-02 22:27 ` [PATCH] firewire: introduce fw_driver.probe and .remove methods Stefan Richter
2013-06-02 22:32 ` [PATCH] firewire: remove support of fw_driver.driver.probe " Stefan Richter
2013-06-02 22:38 ` [PATCH] firewire: introduce fw_driver.probe " Greg Kroah-Hartman
2013-06-02 23:35 ` Stefan Richter
2013-06-03 3:59 ` Takashi Sakamoto
2013-06-09 17:03 ` Stefan Richter
2013-06-03 7:17 ` Clemens Ladisch [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=51AC4308.2030200@ladisch.de \
--to=clemens@ladisch.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=o-takashi@sakamocchi.jp \
--cc=peter@hurleysoftware.com \
--cc=stefanr@s5r6.in-berlin.de \
/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.