On Sat, Jul 09, 2005 at 06:37:10PM +0200, Arjan van de Ven wrote: > On Sat, 2005-07-09 at 12:27 -0400, Ben Collins wrote: > > If it was orphaned it was done so mistakenly. I maintain that code, and > > linux1394. > > > > Aside from that, the the change was pushed into the mainstream kernel > > without going through our repository, which means it would have been > > caught before going to all of our users (most of users of ieee1394 on > > linux use it for sbp2). > > > > THese changes break sbp2, and we'll need to revert them in the main stream > > kernel until the patch is tested and fixed in our tree. > > > > you can't revert the changes done to the locking really.... the API > changed. Also I can't imagine these breaking at all. > > Does ieee1394 tree have a git tree that james could pull? (like akpm > pulls many trees I guess at least sbp2 should be pulled into the scsi > tree) No git tree, we've been strictly subversion lately. I may end up creating a script to sync a git tree soon. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/ - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html