From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/7] ak4114 - fix errors in output selector bits
Date: Wed, 23 Sep 2009 11:32:45 +0200 [thread overview]
Message-ID: <4AB9EB3D.8060002@ivitera.com> (raw)
In-Reply-To: <s5hiqfa9fui.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Wed, 23 Sep 2009 11:16:01 +0200,
> Pavel Hofman wrote:
>> Takashi Iwai wrote:
>>> At Mon, 21 Sep 2009 20:38:08 +0200,
>>>> Do you have any idea when we can expect the changes to propagate to
>>>> http://git.alsa-project.org/?p=alsa-kmirror.git;a=summary so that people
>>>> can install using description in
>>>> http://alsa-project.org/main/index.php/GIT_Server#Occasional_Developers ?
>>> Use sound-2.6.git tree on kernel.org together with alsa-driver-build.git
>>> tree:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
>>> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver-build.git
>>>
>>> For casual developers, the snapshot tarball is available at:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
>>>
>>>
>> Hi Takashi,
>>
>> Thanks a lot for the info. Is this procedure a temporary, alternative,
>> or new preferred way of compiling alsa drivers from git, as opposed to
>> http://alsa-project.org/main/index.php/GIT_Server#Occasional_Developers?
>
> Well, my trees have been over years, and that's where linux-next tree
> is based on, so they are no temporary stuff, at least :)
>
>
> Takashi
Thanks for the info. How do commits from your tree get to
http://git.alsa-project.org/?p=alsa-kmirror.git ?
The point is people ask how they can test new drivers and information on
alsa-project.org for occasional devs talks only about the alsa-project git.
I would update that wiki if I knew the details.
Thanks,
Pavel.
next prev parent reply other threads:[~2009-09-23 9:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 20:25 [PATCH 1/7] ak4114 - fix errors in output selector bits pavel.hofman
2009-09-16 20:25 ` [PATCH 2/7] ak4620 support, codec regs listed in proc pavel.hofman
2009-09-16 20:25 ` [PATCH 3/7] ak4113 support pavel.hofman
2009-09-16 20:25 ` [PATCH 4/7] ice1724 - adding GPIO routines for mask and direction pavel.hofman
2009-09-16 20:25 ` [PATCH 5/7] ice1724 - pro-rate-locking makes sense only for internal clock mode pavel.hofman
2009-09-16 20:25 ` [PATCH 6/7] Support for multiple external clock types pavel.hofman
2009-09-16 20:25 ` [PATCH 7/7] Infrasonic Quartet support pavel.hofman
2009-09-21 14:10 ` [PATCH 1/7] ak4114 - fix errors in output selector bits Takashi Iwai
2009-09-21 18:38 ` Pavel Hofman
2009-09-21 19:26 ` Takashi Iwai
2009-09-23 9:16 ` Pavel Hofman
2009-09-23 9:21 ` Takashi Iwai
2009-09-23 9:32 ` Pavel Hofman [this message]
2009-09-23 9:56 ` Takashi Iwai
2009-10-01 20:06 ` Compilation procedure from git/tiwai/sound-2.6.git Pavel Hofman
2009-10-02 5:49 ` Takashi Iwai
2009-10-02 9:32 ` Pavel Hofman
2009-10-06 13:28 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-09-15 22:39 [PATCH 1/7] ak4114 - fix errors in output selector bits pavel.hofman
2009-09-16 6:03 ` Takashi Iwai
2009-09-16 7:00 ` Pavel Hofman
2009-09-16 7:45 ` Takashi Iwai
2009-09-16 7:48 ` Pavel Hofman
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=4AB9EB3D.8060002@ivitera.com \
--to=pavel.hofman@ivitera.com \
--cc=alsa-devel@alsa-project.org \
--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