From: Keith Packard <keithp@keithp.com>
To: Rohit Jain <rohit.jain@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH vlvdc 1/2] drm/i915: VBT Parser cleanup for eDP block
Date: Fri, 13 Jan 2012 08:38:34 -0800 [thread overview]
Message-ID: <86obu736d1.fsf@sumi.keithp.com> (raw)
In-Reply-To: <1326350984-5368-1-git-send-email-rohit.jain@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 362 bytes --]
On Thu, 12 Jan 2012 12:19:44 +0530, Rohit Jain <rohit.jain@intel.com> wrote:
> Support for parsing parameters for S3D support and T3 optimization
> support is implemented. The order for the bdb_edp struct was also
> made similar to that indicated in spec.
Merged.
7885d20..96c0a2f drm-intel-fixes -> drm-intel-fixes
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2012-01-13 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 6:49 [PATCH vlvdc 1/2] drm/i915: VBT Parser cleanup for eDP block Rohit Jain
2012-01-13 16:38 ` Keith Packard [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=86obu736d1.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rohit.jain@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