From: Damien Lespiau <damien.lespiau@intel.com>
To: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH edid-decode] Read extension blocks in xrandr EDID property
Date: Tue, 17 Dec 2013 23:37:10 +0000 [thread overview]
Message-ID: <20131217233710.GA22746@strange.amr.corp.intel.com> (raw)
In-Reply-To: <1385465149-4331-1-git-send-email-simon.farnsworth@onelan.co.uk>
On Tue, Nov 26, 2013 at 11:25:49AM +0000, Simon Farnsworth wrote:
> Extend the parsing of the xrandr EDID property block to read extension
> blocks, not just the basic block.
>
> Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
Hi,
That patch seems to work as intended, so pushed it with my r-b tag.
Sorry it took so long.
--
Damien
prev parent reply other threads:[~2013-12-17 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 11:25 [PATCH edid-decode] Read extension blocks in xrandr EDID property Simon Farnsworth
2013-12-17 23:37 ` Damien Lespiau [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=20131217233710.GA22746@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=simon.farnsworth@onelan.co.uk \
/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).