From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/dp: Clarify automated test constant and add constant for FAUX test pattern
Date: Tue, 17 Dec 2013 11:32:45 -0800 [thread overview]
Message-ID: <20131217113245.2836ac78@jbarnes-desktop> (raw)
In-Reply-To: <87fvsd33q2.fsf@intel.com>
On Mon, 07 Oct 2013 11:05:57 +0300
Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Fri, 04 Oct 2013, Todd Previte <tprevite@gmail.com> wrote:
> > - DP_TEST_LINK_PATTERN is ambiguous, rename to DP_TEST_LINK_VIDEO_PATTERN to clarify
> > - Added DP_TEST_LINK_FAUX_PATTERN to support automated testing of Fast AUX
> >
> > Signed-off-by: Todd Previte <tprevite@gmail.com>
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Did this ever go in?
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2013-12-17 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 19:59 [PATCH] drm/dp: Clarify automated test constant and add constant for FAUX test pattern Todd Previte
2013-10-07 8:05 ` Jani Nikula
2013-12-17 19:32 ` Jesse Barnes [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=20131217113245.2836ac78@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
/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