On Thu, Dec 08, 2011 at 02:16:10PM -0600, Ramirez Luna, Omar wrote: > On Thu, Dec 8, 2011 at 2:11 PM, Felipe Contreras > <felipe.contreras@xxxxxxxxx> wrote: > > On Sat, Nov 19, 2011 at 12:18 AM, Omar Ramirez Luna <omar.ramirez@xxxxxx> wrote: > >> Given that dm timer framework doesn't support request of clocks > >> by soft | hard irqs because some recent changes, tidspbridge needs > >> to request its clocks on init and enable/disable them on demand. > >> > >> This was first seen on 3.2-rc1. > >> > >> Signed-off-by: Omar Ramirez Luna <omar.ramirez@xxxxxx> > > > > Tested-by: Felipe Contreras <felipe.contreras@xxxxxxxxx> > > Reviewed-by: Felipe Contreras <felipe.contreras@xxxxxxxxx> > > Thanks! > > > Something the commit message didn't mention is that this fixes a nasty > > continuous loop that happens as soon as you load the module. > > Indeed. > > > Definitely 3.2-fix material IMO :) > > I believe it was pushed to staging-next... I'm rooting so it can be > pushed to staging-linus :) As it wasn't originally stated that this was a problem that needed to be fixed for 3.2, can it wait for 3.3-rc1? Especially given that there is still discussion about this? thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
