From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>,
Robert Tarasov <tutankhamen@chromium.org>
Cc: Dave Airlie <airlied@redhat.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/udl: Refactor edid retreiving in UDL driver
Date: Fri, 15 Mar 2019 11:55:27 +0200 [thread overview]
Message-ID: <87k1h0h374.fsf@intel.com> (raw)
In-Reply-To: <CAPM=9twJ2AZ3GNmT0rHxGS8OMgUfLSOn0Mn5KQ9MRkvM1DVrxw@mail.gmail.com>
On Fri, 15 Mar 2019, Dave Airlie <airlied@gmail.com> wrote:
> On Thu, 14 Mar 2019 at 18:25, Robert Tarasov <tutankhamen@chromium.org> wrote:
>>
>> Now drm/udl driver uses drm_do_get_edid() function to retreive and
>> validate all blocks of EDID data. Old approach had insufficient
>> validation routine and had problems with retreiving of extra blocks
>>
>> Signed-off-by: Robert Tarasov <tutankhamen@chromium.org>
>
> Reviewed-by: Dave Airlie <airlied@redhat.com>
>
> I've posted two other udl fixes this morning to actually make my udl work again.
I've reviewed this one as well, but my rb wasn't included in the
repost. Also, there's a v2 earlier today, but I didn't have the time to
check what changed, there's no changelog.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-15 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 18:38 [PATCH] drm/udl: Refactor edid retreiving in UDL driver Robert Tarasov
2019-03-15 2:04 ` Dave Airlie
2019-03-15 9:55 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-13 1:04 Robert Tarasov
2019-03-13 9:27 ` Jani Nikula
2019-03-13 18:36 ` Robert Tarasov
2019-03-14 10:00 ` Jani Nikula
2019-03-14 10:46 ` Hans de Goede
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=87k1h0h374.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tutankhamen@chromium.org \
/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.