Hi Chris On Thu, 14 Jul 2011, Chris Ball wrote: > Hi Guennadi, > > On Thu, Jul 14 2011, Guennadi Liakhovetski wrote: > > There go two more bug-fixes for tmio on top of my earlier patches from > > today, so, should still be easy enough to trace. So, to pull them > > together, the previous ones were > > > > [PATCH v3] mmc: tmio: fix recursive spinlock, don't schedule with > > interrupts disabled > > [PATCH v3] mmc: tmio: maximize power saving > > > > And now follow > > > > [PATCH 1/2] mmc: tmio: fix a recently introduced bug in DMA code > > [PATCH 2/2] mmc: tmio: fix a deadlock > > Pushed these four plus "mmc: sh_mmcif: maximize power saving" to > mmc-next for 3.1. Thanks! Thanks for a fast reaction. > By the way, feel free to send me a MAINTAINERS update taking over > TMIO if you'd like to; you've been doing the work. :-) Thanks for the offer, I appreciate it! I am not the only active tmio mmc contributor, but yes, I could take that role upon me, if noone objects. Would be good to hear, what Ian thinks? Is he maybe still planning to actively working on the driver? Would he like to stay listed as a co-maintainer? If I am to maintain the driver alone, it would be good to have access to some non-sh-mobile hardware, using it too, at least for regression testing. Any idea where to get anything like that? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
