From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Clemens Ladisch <clemens@ladisch.de>,
Peter Hurley <peter@hurleysoftware.com>
Subject: Re: [PATCH] firewire: introduce fw_driver.probe and .remove methods
Date: Sun, 9 Jun 2013 19:03:57 +0200 [thread overview]
Message-ID: <20130609190357.399faea8@stein> (raw)
In-Reply-To: <51AC14B4.4050003@sakamocchi.jp>
I pushed the branch "fw_driver-api-transition" out to linux1394.git at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git fw_driver-api-transition
This branch originates from v3.10-rc5 and contains only the single patch
"firewire: introduce fw_driver.probe and .remove methods".
If you pull this branch, you _can_ move your drivers to the new methods.
Furthermore, the "master" and "for-next" branches at linux1394.git are
now based on "fw_driver-api-transition" and contain patch "firewire:
remove support of fw_driver.driver.probe and .remove methods".
This means that starting from tomorrow, any FireWire driver which goes into
linux-next _must_ implement the new methods.
--
Stefan Richter
-=====-===-= -==- -=--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2013-06-09 17:04 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 [this message]
2013-06-03 7:17 ` Clemens Ladisch
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=20130609190357.399faea8@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=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 \
/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