From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: warn about invalid pfit modes
Date: Thu, 25 Apr 2013 22:20:51 +0200 [thread overview]
Message-ID: <20130425202051.GL6169@phenom.ffwll.local> (raw)
In-Reply-To: <1366919703-20309-3-git-send-email-jbarnes@virtuousgeek.org>
On Thu, Apr 25, 2013 at 12:55:03PM -0700, Jesse Barnes wrote:
> We prevent invalid ones from getting here in the first place, but it
> doesn't hurt to have an extra sanity check.
>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Merged all three, with the first one a bit bikeshedded (as discussed on
irc).
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-04-25 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 19:55 [PATCH 1/3] drm/i915: factor out GMCH panel fitting code and use for eDP v3 Jesse Barnes
2013-04-25 19:55 ` [PATCH 2/3] drm/i915: move PCH pfit controls into pipe_config Jesse Barnes
2013-05-02 22:02 ` Paulo Zanoni
2013-05-03 8:10 ` Daniel Vetter
2013-04-25 19:55 ` [PATCH 3/3] drm/i915: warn about invalid pfit modes Jesse Barnes
2013-04-25 20:20 ` 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=20130425202051.GL6169@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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