From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
"the regression was Cc: stable, too" <stable@kernel.org>
Subject: Re: [PATCH] drm/i915: don't clobber the pipe param in sanitize_modesetting
Date: Sat, 19 May 2012 22:47:19 +0200 [thread overview]
Message-ID: <20120519204719.GC4738@phenom.ffwll.local> (raw)
In-Reply-To: <1336941249_10082@CP5-2952>
On Sun, May 13, 2012 at 09:33:42PM +0100, Chris Wilson wrote:
> On Sun, 13 May 2012 22:29:25 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > ... we need it later on in the function to clean up pipe <-> plane
> > associations. This regression has been introduced in
> >
> > commit f47166d2b0001fcb752b40c5a2d4db986dfbea68
> > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > Date: Thu Mar 22 15:00:50 2012 +0000
> >
> > drm/i915: Sanitize BIOS debugging bits from PIPECONF
> >
> > Spotted by staring at debug output of an (as it turns out) totally
> > unrelated bug.
> >
> > v2: I've totally failed to do the s/pipe/i/ correctly, spotted by
> > Chris Wilson.
> >
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: stable@kernel.org (the regression was Cc: stable, too)
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Queued for -next, thanks for the review.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-05-19 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 20:08 [PATCH] drm/i915: don't clobber the pipe param in sanitize_modesetting Daniel Vetter
2012-05-13 20:12 ` Chris Wilson
2012-05-13 20:29 ` Daniel Vetter
2012-05-13 20:33 ` Chris Wilson
2012-05-19 20:47 ` Daniel Vetter [this message]
2012-05-13 23:41 ` Eugeni Dodonov
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=20120519204719.GC4738@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@kernel.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.