On Thu, Apr 05, 2012 at 11:51:30AM -0500, Rob Clark wrote: > On Thu, Apr 5, 2012 at 11:41 AM, Greg KH <greg@xxxxxxxxx> wrote: > > On Thu, Apr 05, 2012 at 10:34:56AM -0500, Rob Clark wrote: > >> From: Rob Clark <rob@xxxxxx> > >> > >> Not sure what triggered the change in behavior, but seems to > >> result in recursively acquiring a mutex and hanging on boot. But > >> omap_drm_init() seems a much more sane place to register the > >> driver for the DMM sub-device. > >> --- > >> drivers/staging/omapdrm/omap_drv.c | 7 ++++--- > >> 1 files changed, 4 insertions(+), 3 deletions(-) > > > > Is this needed for 3.4-final? Any older kernels like 3.3 as well? > > Yeah, it is needed for 3.4-final.. I need to check on 3.3 (it was > fine circa 3.3-rc6 or rc7) Ok, I'll queue it up for 3.4-final, let me know if it's also needed in 3.3 if you get the chance. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
