All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, stefanr@s5r6.in-berlin.de,
	clemens@ladisch.de, ffado-devel@lists.sf.net
Subject: Re: [PATCH 0/4 v5] ALSA: dice: improve card registration processing
Date: Wed, 06 Jan 2016 14:04:16 +0100	[thread overview]
Message-ID: <s5hfuyasvu7.wl-tiwai@suse.de> (raw)
In-Reply-To: <568CF159.80202@sakamocchi.jp>

On Wed, 06 Jan 2016 11:50:01 +0100,
Takashi Sakamoto wrote:
> 
> Hi,
> 
> On Jan 06 2016 18:19, Takashi Iwai wrote:
> > On Thu, 31 Dec 2015 05:58:10 +0100,
> > Takashi Sakamoto wrote:
> >>
> >> Hi,
> >>
> >> This patchset updates my previous one:
> >> [alsa-devel] [PATCH 0/5 v4] ALSA: dice: improve card registration processing
> >> a
> >>
> >> Changes:
> >>  * Merge patch 02 and 03 in v4.
> >>  * Allocate sound card instance in sound card registration work, independently
> >>    of dice instance, allocated in .probe callback and set as driver_data of
> >>    device structure.
> >>  * Use __be32 type for __be32 data.
> >>
> >> In this version, sound card instance is not allocated in .probe callback. In
> >> the callback, dice instance is allocated independently of the card instance.
> >> Thus, in .probe callback, this driver reserve no slot of sound card. The
> >> allocation of sound card instance is performed in a scheduled work. When
> >> processing in the work fails, the work can be re-scheduled again according to
> >> bus reset.
> > 
> > Applied now all four patches.  Thanks.
> 
> OK. Thanks.
> 
> How about the rest of my work for ALSA Dice driver to Linux 4.5?
> 
> [alsa-devel] [RFC][PATCH 00/10 v2] ALSA: dice: stabiliza packet streaming
> http://mailman.alsa-project.org/pipermail/alsa-devel/2015-December/101897.html
> 
> It takes almost one month since I posted the RFCv2. We already had a
> discussion about the patchset in RFCv1 and in my opinion there's no
> thorough disagreement. If possible, I'd like to merge it in the merge
> window for Linux 4.5. If we go for it, I'll post them in this night.

Well, RFC is RFC and not for merging.  If it's meant for merging,
let's poke relevant people whether it's OK.


Takashi

  reply	other threads:[~2016-01-06 13:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31  4:58 [PATCH 0/4 v5] ALSA: dice: improve card registration processing Takashi Sakamoto
2015-12-31  4:58 ` [PATCH 1/4] ALSA: dice: split subaddress check from category check Takashi Sakamoto
2015-12-31  4:58 ` [PATCH 2/4] ALSA: dice: postpone card registration Takashi Sakamoto
2015-12-31  4:58 ` [PATCH 3/4] ALSA: dice: purge transaction initialization at timeout of Dice notification Takashi Sakamoto
2015-12-31  4:58 ` [PATCH 4/4] ALSA: dice: expand timeout to wait for " Takashi Sakamoto
2016-01-06  9:19 ` [PATCH 0/4 v5] ALSA: dice: improve card registration processing Takashi Iwai
2016-01-06 10:50   ` Takashi Sakamoto
2016-01-06 13:04     ` Takashi Iwai [this message]
2016-01-07  0:21       ` Takashi Sakamoto
2016-01-07  7:47         ` 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=s5hfuyasvu7.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=ffado-devel@lists.sf.net \
    --cc=o-takashi@sakamocchi.jp \
    --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.