Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Anderegg <rolf.anderegg@weiss.ch>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Brian Karr <briank@tctechnologies.tc>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: firewire-kernel-streaming branch into main kernel tree?
Date: Mon, 10 Jun 2013 16:51:33 +0200	[thread overview]
Message-ID: <51B5E7F5.7040800@weiss.ch> (raw)
In-Reply-To: <5148777B.3010006@ladisch.de>


> For those devices, merging would make sense now.  So would you be happy
> if I merged the driver in its current form, except being restricted to
> all/some(?) Weiss devices?

Our findings have shown that snd-dice works with all our DICE based Weiss
devices, as far as playback (with sync-source restricted to CLOCK_SOURCE_ARX1)
is concerned. So yes, we would be very happy with a merge of the driver's
current form.

Regards,
Rolf

      reply	other threads:[~2013-06-10 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 12:25 firewire-kernel-streaming branch into main kernel tree? Rolf Anderegg
2013-03-19 14:34 ` Clemens Ladisch
2013-06-10 14:51   ` Rolf Anderegg [this message]

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=51B5E7F5.7040800@weiss.ch \
    --to=rolf.anderegg@weiss.ch \
    --cc=alsa-devel@alsa-project.org \
    --cc=briank@tctechnologies.tc \
    --cc=clemens@ladisch.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