From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org,
linux1394-devel@lists.sourceforge.net, ffado-devel@lists.sf.net
Subject: Re: [PATCH 0/5 v2] ALSA: firewire-lib: purge restriction of synchronization for non-blocking mode
Date: Sat, 23 May 2015 09:16:12 +0200 [thread overview]
Message-ID: <s5hlhgf3gsj.wl-tiwai@suse.de> (raw)
In-Reply-To: <1432303254-4192-1-git-send-email-o-takashi@sakamocchi.jp>
At Fri, 22 May 2015 23:00:49 +0900,
Takashi Sakamoto wrote:
>
> This patchset renews my previous one.
>
> [alsa-devel] [PATCH 0/4] firewire-lib: purge restriction of synchronization for non-blocking mode
> http://mailman.alsa-project.org/pipermail/alsa-devel/2015-May/092086.html
>
> Changes:
> * Use stack to keep calculation result per callback of isochronous receive context.
> * Fix my stupid mistake to compare byte count to quadlet count. (oh...)
> * Rename flag to proper name.
> * Add 4th patch newly for better reading.
Applied all five patches now.
thanks,
Takashi
>
>
> Takashi Sakamoto (5):
> ALSA: firewire-lib: add buffer-over-run protection at receiving more
> data blocks than expected
> ALSA: firewire-lib: simplify function to calculate the number of data
> blocks
> ALSA: firewire-lib: pass the number of data blocks in incoming packets
> to outgoing packets
> ALSA: firewire-lib: set streaming error outside of packetization
> ALSA: firewire-lib: remove restriction for non-blocking mode
>
> sound/firewire/amdtp.c | 151 ++++++++++++++++++++++++--------------
> sound/firewire/amdtp.h | 4 +
> sound/firewire/oxfw/oxfw-stream.c | 10 ++-
> 3 files changed, 106 insertions(+), 59 deletions(-)
>
> --
> 2.1.4
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
next prev parent reply other threads:[~2015-05-23 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 14:00 [PATCH 0/5 v2] ALSA: firewire-lib: purge restriction of synchronization for non-blocking mode Takashi Sakamoto
2015-05-22 14:00 ` [PATCH 1/5] ALSA: firewire-lib: add buffer-over-run protection at receiving more data blocks than expected Takashi Sakamoto
2015-05-22 14:00 ` [PATCH 2/5] ALSA: firewire-lib: simplify function to calculate the number of data blocks Takashi Sakamoto
2015-05-22 14:00 ` [PATCH 3/5] ALSA: firewire-lib: pass the number of data blocks in incoming packets to outgoing packets Takashi Sakamoto
2015-05-22 14:00 ` [PATCH 4/5] ALSA: firewire-lib: set streaming error outside of packetization Takashi Sakamoto
2015-05-22 14:00 ` [PATCH 5/5] ALSA: firewire-lib: remove restriction for non-blocking mode Takashi Sakamoto
2015-05-23 7:16 ` Takashi Iwai [this message]
2015-05-25 15:12 ` [PATCH 0/5 v2] ALSA: firewire-lib: purge restriction of synchronization " Takashi Sakamoto
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=s5hlhgf3gsj.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=ffado-devel@lists.sf.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=o-takashi@sakamocchi.jp \
/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.