All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: abhinavk@codeaurora.org, dri-devel@lists.freedesktop.org
Cc: adelva@google.com, linux-arm-msm@vger.kernel.org,
	seanpaul@chromium.org, aravindh@codeaurora.org,
	Uma Shankar <uma.shankar@intel.com>
Subject: Re: [PATCH v2] drm: Parse Colorimetry data block from EDID
Date: Mon, 03 Feb 2020 12:32:54 -0800	[thread overview]
Message-ID: <5e388377.1c69fb81.e9add.a3d4@mx.google.com> (raw)
In-Reply-To: <90542e32913e315bae02865e1d18a622@codeaurora.org>

Quoting abhinavk@codeaurora.org (2020-01-31 13:01:38)
> Hi Steven
> 
> Any further comments on this change?
> 

No. I was more of a drive by review comment on the previous patch.


WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <swboyd@chromium.org>
To: abhinavk@codeaurora.org, dri-devel@lists.freedesktop.org
Cc: adelva@google.com, linux-arm-msm@vger.kernel.org,
	aravindh@codeaurora.org, seanpaul@chromium.org,
	Uma Shankar <uma.shankar@intel.com>
Subject: Re: [PATCH v2] drm: Parse Colorimetry data block from EDID
Date: Mon, 03 Feb 2020 12:32:54 -0800	[thread overview]
Message-ID: <5e388377.1c69fb81.e9add.a3d4@mx.google.com> (raw)
In-Reply-To: <90542e32913e315bae02865e1d18a622@codeaurora.org>

Quoting abhinavk@codeaurora.org (2020-01-31 13:01:38)
> Hi Steven
> 
> Any further comments on this change?
> 

No. I was more of a drive by review comment on the previous patch.

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-02-03 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 23:40 [PATCH v2] drm: Parse Colorimetry data block from EDID Abhinav Kumar
2020-01-27 23:40 ` Abhinav Kumar
2020-01-31 21:01 ` abhinavk
2020-01-31 21:01   ` abhinavk
2020-02-03 20:32   ` Stephen Boyd [this message]
2020-02-03 20:32     ` Stephen Boyd

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=5e388377.1c69fb81.e9add.a3d4@mx.google.com \
    --to=swboyd@chromium.org \
    --cc=abhinavk@codeaurora.org \
    --cc=adelva@google.com \
    --cc=aravindh@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=seanpaul@chromium.org \
    --cc=uma.shankar@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.