Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Wang Xingchao <xingchao.wang@intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
	paulo.r.zanoni@intel.com
Subject: Re: [PATCH] drm/i915: HDMI/DP - ELD info refresh support for Haswell
Date: Tue, 22 Jan 2013 20:08:14 +0100	[thread overview]
Message-ID: <20130122190814.GL31870@phenom.ffwll.local> (raw)
In-Reply-To: <1358868325-8110-1-git-send-email-xingchao.wang@intel.com>

On Tue, Jan 22, 2013 at 11:25:25PM +0800, Wang Xingchao wrote:
> ELD info should be updated dynamically according to hot plug event.
> For haswell chip, clear/set the eld valid bit and output enable bit
> from callback intel_disable/eanble_ddi().
> 
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
> Signed-off-by: Wang Xingchao <xingchao.wang@intel.com>

Queued for -next, thanks for the patch. For further patches please include
an in-patch changelog for the different patch iterations, that way it's
really clear what (and why) something changed compared to a previous patch
submission. Otherwise if a patch later on causes issues or is unclear why
we need a given piece of code it's much more work to dig out the old
discussions and conclusions.

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-01-22 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 15:25 [PATCH] drm/i915: HDMI/DP - ELD info refresh support for Haswell Wang Xingchao
2013-01-22 19:08 ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-07  5:20 Wang Xingchao
2013-01-14 17:00 ` Rodrigo Vivi
2013-01-18  2:49   ` Wang, Xingchao

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=20130122190814.GL31870@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=xingchao.wang@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