Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: daniel.vetter@ffwll.ch,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fixup sbi_read/write locking
Date: Wed, 23 Jan 2013 00:53:32 +0100	[thread overview]
Message-ID: <20130122235332.GP31870@phenom.ffwll.local> (raw)
In-Reply-To: <20130122154214.71a71446@bwidawsk.net>

On Tue, Jan 22, 2013 at 03:42:14PM -0800, Ben Widawsky wrote:
> On Tue, 22 Jan 2013 15:33:27 +0100
> daniel.vetter@ffwll.ch wrote:
> 
> > From: Daniel Vetter <daniel.vetter@ffwll.ch>
> > 
> > commit 09153000b8ca32a539a1207edebabd0d40b6c61b
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date:   Wed Dec 12 14:06:44 2012 +0100
> > 
> >     drm/i915: rework locking for intel_dpio|sbi_read|write
> > 
> > reworked the locking around sbi_read/write functions for 3.8-fixes.
> > But
> > 
> > commit dde86e2db54545ef981b64805097a7b4c3156d6e
> > Author: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > Date:   Sat Dec 1 12:04:25 2012 -0200
> > 
> >     drm/i915: add lpt_init_pch_refcl
> > 
> > Added new use-cases in the -next tree which has not been updated in
> > the merge. Fix it up.
> > 
> > Reported-by: Ben Widawsky <ben@bwidawsk.net>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
> Tested-by: Ben Widawsky <ben@bwidawsk.net>

Queued for -next, thanks for the review.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2013-01-22 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 14:33 [PATCH] drm/i915: fixup sbi_read/write locking daniel.vetter
2013-01-22 23:42 ` Ben Widawsky
2013-01-22 23:53   ` Daniel Vetter [this message]

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=20130122235332.GP31870@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --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