linux-kernel - Re: [PATCH] firewire: introduce fw_driver.probe and .remove methods

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <51AC4308.2030200@ladisch.de>
Date:	Mon, 03 Jun 2013 09:17:28 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
CC:	Takashi Sakamoto <o-takashi@...amocchi.jp>,
	linux1394-devel@...ts.sourceforge.net,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org,
	Peter Hurley <peter@...leysoftware.com>
Subject: Re: [PATCH] firewire: introduce fw_driver.probe and .remove methods

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@...isch.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/