From: Chris Wilson <chris@chris-wilson.co.uk>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] drm/i915: don't grab dev->struct_mutex for userspace forcewak
Date: Fri, 10 Aug 2012 23:22:15 +0100 [thread overview]
Message-ID: <1344637338_72217@CP5-2952> (raw)
In-Reply-To: <1344544438-5654-1-git-send-email-daniel.vetter@ffwll.ch>
On Thu, 9 Aug 2012 22:33:58 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Since forcewake is now protected by a spinlock, we don't need to grab
> dev->struct_mutex any more. This way we can also get rid of a stale
> comment, noticed by Ben Widawsky while reviewing some locking changes.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
(Although I still wish it were not so)
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-10 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 20:33 [PATCH] drm/i915: don't grab dev->struct_mutex for userspace forcewak Daniel Vetter
2012-08-10 22:22 ` Chris Wilson [this message]
2012-08-11 20:23 ` Daniel Vetter
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=1344637338_72217@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox