From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fixup forcewake spinlock fallout in drpc debugfs function
Date: Wed, 25 Jan 2012 08:45:27 -0800 [thread overview]
Message-ID: <4F2031A7.4080903@bwidawsk.net> (raw)
In-Reply-To: <1327495963-2794-1-git-send-email-daniel.vetter@ffwll.ch>
On 01/25/12 04:52, Daniel Vetter wrote:
> My forcewake spinlock patches have a functional conflict with Ben
> Widawsky's gen6 drpc support for debugfs. Result was a benign warning
> about trying to read an non-atomic variabla with atomic_read.
>
> Note that the entire check is racy anyway and purely informational.
> Also update it to reflect the forcewake voodoo changes, the kernel can
> now also hold onto a forcewake reference for longer times.
>
> Signed-Off-by: Daniel Vetter<daniel.vetter@ffwll.ch>
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
next prev parent reply other threads:[~2012-01-25 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 12:52 [PATCH] drm/i915: fixup forcewake spinlock fallout in drpc debugfs function Daniel Vetter
2012-01-25 16:45 ` Ben Widawsky [this message]
2012-01-25 17:16 ` Keith Packard
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=4F2031A7.4080903@bwidawsk.net \
--to=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 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.