On Thu, 7 Feb 2008, Takashi Iwai wrote: > At Thu, 7 Feb 2008 05:41:57 -0800 (PST), > Trent Piepho wrote: > > > > On Thu, 7 Feb 2008, Takashi Iwai wrote: > > > At Thu, 7 Feb 2008 05:10:27 -0800 (PST), > > > > It would also be a huge PITA for developers who work on multiple > > > > sub-systems. If I want to make a patch for an alsa driver, I have to > > > > reboot into an alsa kernel? I try to go a few months between rebooting. > > > > > > Hm, what's the problem to pull alsa.git tree to your own working tree? > > > > How do I test the driver if it's compiled with the kernel in the alsa.git > > tree? I want to compile the driver against the kernel I'm running now. > > Well, I don't get your point. "git-pull alsa.git" onto your current > kernel tree and make. Then you have the latest ALSA drivers for your > current system... Pull cannot be used. You'll pull also Linus's changes in tree with this command (which might not be wanted). We'll provide a GNU patch interface to patch your tree as required hidding used SCM system, of course. Jaroslav ----- Jaroslav Kysela <perex@xxxxxxxx> Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
