From: Clemens Ladisch <clemens@ladisch.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
linux1394-devel@lists.sourceforge.net, ffado-devel@lists.sf.net
Subject: Re: [PATCH 0/4] ALSA: fireworks/bebob/dice/oxfw: fix kernel oops at unplugging during streaming
Date: Sun, 22 Feb 2015 00:06:32 +0100 [thread overview]
Message-ID: <54E90F78.7040803@ladisch.de> (raw)
In-Reply-To: <1424530500-9116-1-git-send-email-o-takashi@sakamocchi.jp>
Takashi Sakamoto wrote:
> With this patchset, each driver keeps a reference to FireWire unit till
> all of ALSA applications close its character devices. This may be against
> IEEE 1394 bus driver developers' expectation to high-level drivers.
The fw_unit reference counting was designed for situations like this.
Regards,
Clemens
next prev parent reply other threads:[~2015-02-21 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 14:54 [PATCH 0/4] ALSA: fireworks/bebob/dice/oxfw: fix kernel oops at unplugging during streaming Takashi Sakamoto
2015-02-21 14:54 ` [PATCH 1/4] ALSA: fireworks/bebob/dice/oxfw: add reference-counting for FireWire unit Takashi Sakamoto
2015-02-21 14:54 ` [PATCH 2/4] ALSA: firewire-lib: remove reference counting Takashi Sakamoto
2015-02-21 14:54 ` [PATCH 3/4] ALSA: fireworks/bebob/dice/oxfw: allow stream destructor after releasing runtime Takashi Sakamoto
2015-02-21 14:55 ` [PATCH 4/4] ALSA: fireworks/bebob/dice/oxfw: make it possible to shutdown safely Takashi Sakamoto
2015-02-21 23:06 ` Clemens Ladisch [this message]
2015-02-22 17:36 ` [PATCH 0/4] ALSA: fireworks/bebob/dice/oxfw: fix kernel oops at unplugging during streaming Takashi Iwai
2015-02-22 18:49 ` Clemens Ladisch
2015-02-23 8:18 ` Takashi Iwai
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=54E90F78.7040803@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=ffado-devel@lists.sf.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=o-takashi@sakamocchi.jp \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox