From: Jani Nikula <jani.nikula@linux.intel.com>
To: John Sledge <john_sledget@yahoo.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: DRM Inquiry DPCD
Date: Wed, 23 May 2018 09:41:32 +0300 [thread overview]
Message-ID: <87vabenaar.fsf@intel.com> (raw)
In-Reply-To: <1276988254.133081.1527043373244@mail.yahoo.com>
On Wed, 23 May 2018, John Sledge <john_sledget@yahoo.com> wrote:
> Do you have any suggestions or advice how to use the kernel driver in
> DRM in regards to how to implement the method drm_dp_dpcd_readb for
> example?
Sincerely, my suggestion is to respond and be active when people take
the time to look into your problem and reply to you [1].
BR,
Jani.
[1] http://mid.mail-archive.com/87fu2pxph0.fsf@intel.com
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-05-23 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1276988254.133081.1527043373244.ref@mail.yahoo.com>
2018-05-23 2:42 ` DRM Inquiry DPCD John Sledge
2018-05-23 6:41 ` Jani Nikula [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=87vabenaar.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=john_sledget@yahoo.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;
as well as URLs for NNTP newsgroup(s).