Re: 2.6.12-rc3-mm3: ALSA broken ?

["J.A. Magallon" <jamagallon@able.es>]

On 05.30, Takashi Iwai wrote:
> At Fri, 27 May 2005 21:18:00 +0000,
> J.A. Magallon wrote:
> 
> > Which is the correct way to generate a patch against a kernel tree ?
> 
> Sorry, I don't understand "which" in the above question - do you mean
> alsa-kernel tree or what?  We have a git repository, so that the
> latest ALSA patches can be taken...
> 

Sorry for my bad english...

The correct question is: how do I generate a patch against a given kernel,
from the alsa-driver-x.y.z.tar.gz I can download from alsa.org ?
I thought it was enough to diff -ruN the alsa-kernel dir (minus the Documentation
folder) vs the /usr/src/linux-xxxxx/sound folder.
I have seen that there are some scripts in the tarball that install the new
drivers on a given kernel tree via symlinks, but I would like to get just
a patch. I think I will have to diff selected directories, or create
an exclude list... Are there files that are just copied from mainline and do
not change in ALSA tree, or anything can change under alsa-kernel ?

Now that I think of it, if you work against Linus tree,
would it be more correct to diff against 2.6.12-rc5, and then try to apply
to -rc5-mm1 ? 
Whe you do a release, which is your reference, latest stable (2.6.11),
latest rc or latest git ? 

About git, I don't really like the idea of storing a full kernel tree just
to do 'git update' or the like, and use the 'sound' part.

Thanks.

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandriva Linux release 2006.0 (Cooker) for i586
Linux 2.6.11-jam20 (gcc 4.0.0 (4.0.0-3mdk for Mandriva Linux release 2006.0))