From: Adam Jackson <ajax@redhat.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/dp: downstream port capabilities are not present in DPCD 1.0
Date: Fri, 27 Sep 2013 13:30:12 -0400 [thread overview]
Message-ID: <1380303012.1488.48.camel@dmt> (raw)
In-Reply-To: <1380282522-27826-2-git-send-email-jani.nikula@intel.com>
On Fri, 2013-09-27 at 14:48 +0300, Jani Nikula wrote:
> We haven't read the downstream port caps for DPCD 1.0, so don't use
> them.
>
> v2: use defines for DPCD 1.0 downstream port types
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
I don't know if I've ever seen a DPCD 1.0 device, but the changes make
sense. For the series:
Reviewed-by: Adam Jackson <ajax@redhat.com>
- ajax
next prev parent reply other threads:[~2013-09-27 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 11:48 [PATCH 1/2] drm/dp: add defines for downstream port types Jani Nikula
2013-09-27 11:48 ` [PATCH 2/2] drm/i915/dp: downstream port capabilities are not present in DPCD 1.0 Jani Nikula
2013-09-27 17:30 ` Adam Jackson [this message]
2013-09-27 19:06 ` [PATCH 1/2] drm/dp: add defines for downstream port types Todd Previte
2013-09-27 21:20 ` Alex Deucher
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=1380303012.1488.48.camel@dmt \
--to=ajax@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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