From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/4] drm: handle override/firmware edid at the lowest level
Date: Fri, 17 Feb 2017 17:34:55 +0200 [thread overview]
Message-ID: <20170217153455.GX31595@intel.com> (raw)
In-Reply-To: <1487344854-18777-1-git-send-email-jani.nikula@intel.com>
On Fri, Feb 17, 2017 at 05:20:50PM +0200, Jani Nikula wrote:
> v2 of http://mid.mail-archive.com/cover.1487241304.git.jani.nikula@intel.com
lgtm. For the series
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-17 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 15:20 [PATCH v2 0/4] drm: handle override/firmware edid at the lowest level Jani Nikula
2017-02-17 15:20 ` [PATCH v2 1/4] drm: move edid property update and add modes out of edid firmware loader Jani Nikula
2017-02-17 15:20 ` [PATCH v2 2/4] drm: do not debug log about missing CEA extensions on NULL edid Jani Nikula
2017-02-17 15:20 ` [PATCH v2 3/4] drm/edid: respect connector force for drm_get_edid ddc probe Jani Nikula
2017-02-17 15:20 ` [PATCH v2 4/4] drm: handle override edid and firmware EDID at drm_do_get_edid() level Jani Nikula
2017-02-26 21:22 ` Daniel Vetter
2017-02-27 15:09 ` Ville Syrjälä
2017-02-27 16:19 ` Daniel Vetter
2017-02-27 16:36 ` Ville Syrjälä
2017-02-17 15:34 ` Ville Syrjälä [this message]
2017-02-21 14:15 ` [PATCH v2 0/4] drm: handle override/firmware edid at the lowest level Jani Nikula
2017-02-17 19:22 ` ✓ Fi.CI.BAT: success for drm: handle override/firmware edid at the lowest level (rev2) Patchwork
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=20170217153455.GX31595@intel.com \
--to=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.