From: Greg KH <greg@kroah.com>
To: Rob Clark <rob.clark@linaro.org>
Cc: linux-omap@vger.kernel.org, patches@linaro.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] staging: drm/omap: move where DMM driver is registered
Date: Thu, 5 Apr 2012 09:58:43 -0700 [thread overview]
Message-ID: <20120405165843.GA17004@kroah.com> (raw)
In-Reply-To: <CAF6AEGv7pUht3VkGqobCJd4+KPx2NUoju5++eRUpToAg1ZxPeg@mail.gmail.com>
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@kroah.com> wrote:
> > On Thu, Apr 05, 2012 at 10:34:56AM -0500, Rob Clark wrote:
> >> From: Rob Clark <rob@ti.com>
> >>
> >> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-05 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 15:34 [PATCH] staging: drm/omap: move where DMM driver is registered Rob Clark
2012-04-05 16:41 ` Greg KH
2012-04-05 16:51 ` Rob Clark
2012-04-05 16:58 ` Greg KH [this message]
2012-04-05 17:44 ` Rob Clark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120405165843.GA17004@kroah.com \
--to=greg@kroah.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-omap@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rob.clark@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.