From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: Alsa-devel <alsa-devel@alsa-project.org>,
Krzysztof Helt <krzysztof.h1@poczta.fm>
Subject: Re: [PATCH 2/2] wss: use stuct snd_wss instead of snd_ad1848
Date: Thu, 03 Jul 2008 19:07:38 +0200 [thread overview]
Message-ID: <486D075A.1090409@keyaccess.nl> (raw)
In-Reply-To: <s5hk5g3rv7v.wl%tiwai@suse.de>
On 03-07-08 14:46, Takashi Iwai wrote:
> At Thu, 03 Jul 2008 12:42:00 +0200,
> Rene Herman wrote:
>> Yes these should probably grow as a series with somewhat of a (semi-)
>> final result being apparent after applying patch N of N. I'm importing
>> Krzysztof' patches into a "wss" branch in my local git tree and will be
>> testing them as they come in though -- and frankly, I think it's better
>> if they come in as he does them a few at a time rather than a large
>> number at once as it's easier for review purposes.
>
> Well, I can keep it in a branch if you prefer. Just let me know.
If that is to me specifically, I don't really care. "git am" is a very
useful tool.
>> But as far as I'm concerned you could just sit back until the series is
>> somewhat "complete".
>
> OK. As 2.6.26 will come out soon, it's a bit too late to include
> such a big change for 2.6.27. So we have still some time :)
If Krzysztof is anything like me, he's not mucking around with ISA stuff
due to compatibility with deadlines, so there's even going to be kernels
after 2.6.28 I'd say... :-)
Rene.
next prev parent reply other threads:[~2008-07-03 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 18:14 [PATCH 2/2] wss: use stuct snd_wss instead of snd_ad1848 Krzysztof Helt
2008-07-03 10:07 ` Takashi Iwai
2008-07-03 10:42 ` Rene Herman
2008-07-03 12:46 ` Takashi Iwai
2008-07-03 17:07 ` Rene Herman [this message]
2008-07-03 17:03 ` Krzysztof Helt
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=486D075A.1090409@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=krzysztof.h1@poczta.fm \
--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 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.