On Mon, Oct 18, 2010 at 02:34, Mike Frysinger wrote: > On Mon, Oct 18, 2010 at 02:28, Grant Likely wrote: >> On Sun, Oct 17, 2010 at 06:59:13PM -0400, Mike Frysinger wrote: >>> Quite a bit here, but these patches have been around for a while. The >>> reason they haven't been pushed up before was that some of the first >>> changes introduced known bugs themselves and needed some manual fixing. >>> >>> Also, while some files touch Blackfin headers in arch/blackfin/, I'd >>> like to keep them in this series and merge through the SPI tree to keep >>> conflict issues down, as well as possible breakage due to desync. >>> >>> These are also available in my 'for-spi' branch of my git tree: >>> git://git.kernel.org/pub/scm/linux/kernel/git/vapier/blackfin.git >> >> On brief review, the series looks good with a couple of minor comments >> (already sent). >> >> For the spi branch that I push to Linus, I always use the prefix >> spi/<driver-name>. If the patches in your branch also use that >> prefix, then I'd be happy to pull your tree directly instead of >> committing the patches myself. Otherwise, I need to commit them >> manually. > > merged patches thus far have used the convention i picked here, but i > dont have a problem with changing them.
ive rewriitten the logs, addressed your feedback on all the other patches, and pushed up the new for-spi branch if you want to double check & pull. i dont want to spam people with 30 patches where only the summary changed ... -mike _______________________________________________ Uclinux-dist-devel mailing list Uclinux-dist-devel@blackfin.uclinux.org https://blackfin.uclinux.org/mailman/listinfo/uclinux-dist-devel
