alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Felix Homann <showlabor.felixhomann@googlemail.com>
Cc: tiwai@suse.de, blablack@gmail.com, alsa-devel@alsa-project.org,
	clemens@ladisch.de, gdiffey@gmail.com
Subject: Re: [PATCH 0/6] snd-usb endpoint rework, version 6
Date: Fri, 30 Dec 2011 16:24:23 +0100	[thread overview]
Message-ID: <4EFDD7A7.3010706@gmail.com> (raw)
In-Reply-To: <CAFz=ag6XNJSXvYQnAEbx=M+zXVH7sEw=_CJQKx63MmdQBWFuwA@mail.gmail.com>

On 12/30/2011 04:16 PM, Felix Homann wrote:
> Hi Daniel,
> 
> 2011/12/30 Daniel Mack <zonque@gmail.com>:
>>
>> Any chance that more people who've been waiting for support of the FTU
>> can use the lazy time between the years and quickly test this set?
> 
> Could you please put a combined patch on your github place?

Done:

  https://gist.github.com/1168715

> Should it be OK to use the alsa-driver/alsa-kernel update approach or
> would I need to build a complete kernel image?

Take Linus' tree, merge Takashi's tree (from
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git master)
and then apply the gist.


Daniel

  parent reply	other threads:[~2011-12-30 15:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 16:15 [PATCH 0/6] snd-usb endpoint rework, version 6 Daniel Mack
2011-12-23 16:15 ` [PATCH 1/6] ALSA: snd-usb: add snd_usb_audio-wide mutex Daniel Mack
2011-12-23 16:15 ` [PATCH 2/6] ALSA: snd-usb: implement new endpoint streaming model Daniel Mack
2011-12-23 16:15 ` [PATCH 3/6] ALSA: snd-usb: switch over to new endpoint streaming logic Daniel Mack
2011-12-23 16:15 ` [PATCH 4/6] ALSA: snd-usb: remove old " Daniel Mack
2011-12-23 16:15 ` [PATCH 5/6] ALSA: snd-usb: add support for implicit feedback Daniel Mack
2011-12-23 16:15 ` [PATCH 6/6] ALSA: snd-usb: add some documentation Daniel Mack
2011-12-30 13:56 ` [PATCH 0/6] snd-usb endpoint rework, version 6 Daniel Mack
2011-12-30 15:22   ` Felix Homann
     [not found]   ` <CAFz=ag6XNJSXvYQnAEbx=M+zXVH7sEw=_CJQKx63MmdQBWFuwA@mail.gmail.com>
2011-12-30 15:24     ` Daniel Mack [this message]
     [not found]       ` <CACckToWP-C5H2xhvdJ5ykNf4BcuNCa4cMyFh2hppcwW0u33fQQ@mail.gmail.com>
     [not found]         ` <4EFE6E52.4050503@gmail.com>
2011-12-31  4:35           ` Grant Diffey
2011-12-31  8:04             ` Grant Diffey
2011-12-31 14:23   ` Felix Homann
2011-12-31 15:02     ` Aurélien Leblond
2011-12-31 15:39       ` Felix Homann
     [not found]   ` <CAFz=ag7_qzPJq44havp=EbFVKud5VvKaOLJk0i0dM43X3urp9Q@mail.gmail.com>
2012-01-01 17:09     ` Felix Homann
2012-01-16 20:26       ` Grant Diffey
2012-01-16 20:27         ` Grant Diffey
2012-04-09 19:21         ` Daniel Mack
2012-04-10 15:35           ` Grant Diffey
2012-04-10 18:52           ` Felix Homann
2012-04-11 15:08             ` Daniel Mack
2012-04-12  9:05               ` Felix Homann
2012-04-12 11:45                 ` Daniel Mack
2012-04-10 15:40       ` Grant Diffey
  -- strict thread matches above, loose matches on Subject: below --
2012-02-13 20:41 Aurélien Leblond
2012-02-22 18:50 ` Daniel Mack
2012-03-05  8:01   ` Felix Homann

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=4EFDD7A7.3010706@gmail.com \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=blablack@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=gdiffey@gmail.com \
    --cc=showlabor.felixhomann@googlemail.com \
    --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;
as well as URLs for NNTP newsgroup(s).