At Wed, 23 Apr 2008 11:15:11 +0100, Mark Brown wrote: > > On Wed, Apr 23, 2008 at 10:41:48AM +0200, Takashi Iwai wrote: > > > Actually I have a separate branch on my git tree. The master is for > > mm tree and for-linus is for Linus. The appropriate patches are > > what's the current status of the git trees? There was some talk about > moving the primary revision control system for the kernel bits over to > git during the 2.6.26 cycle. No advance since then unfortuantely. Instead I'm keeping my own git tree for maintenance purpose too: http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git > > My previous comment was about the patch that affects several subsystem > > / arch changes. In this case, the change isn't only in the subsystem > > tree. So, we'd need to cope with others anyway. Keeping such a patch > > in mm tree separately is one option. > > I think that just putting the patches into ALSA is a better bet - it's > more in tune with what most of the other subsystems are doing and it > avoids possible confusion about what's actually made it into -mm. It should be case-by-case, but yes, as long as the patch doesn't break builds, it's no problem to keep it in ALSA tree in general. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
