linux-kernel - Re: [PATCH v1] drm/bridge: it6505: HDCP CTS fail on repeater items

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <nczuje3ur7sf7uqkygtziwnz5p6b4b7bf5on5crljr2ijmblrv@ym3fkvqxbjq5>
Date: Fri, 20 Sep 2024 18:50:05 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Pin-yen Lin <treapking@...omium.org>
Cc: Hermes.Wu@....com.tw, Andrzej Hajda <a.hajda@...sung.com>, 
	Neil Armstrong <narmstrong@...libre.com>, Robert Foss <robert.foss@...aro.org>, 
	Laurent Pinchart <Laurent.pinchart@...asonboard.com>, Jonas Karlman <jonas@...boo.se>, 
	Jernej Skrabec <jernej.skrabec@...il.com>, David Airlie <airlied@...il.com>, 
	Daniel Vetter <daniel@...ll.ch>, "open list:DRM DRIVERS" <dri-devel@...ts.freedesktop.org>, 
	open list <linux-kernel@...r.kernel.org>, Kenneth hung <kenneth.hung@....com.tw>
Subject: Re: [PATCH v1] drm/bridge: it6505: HDCP CTS fail on repeater items

On Fri, Sep 20, 2024 at 01:27:54PM GMT, Pin-yen Lin wrote:
> On Thu, Sep 19, 2024 at 10:58 AM <Hermes.Wu@....com.tw> wrote:
> >
> > From: Hermes Wu <Hermes.Wu@....com.tw>
> >
> > Fix HDCP CTS items on UNIGRAF DPR-100.
> >
> > Signed-off-by: Hermes Wu <Hermes.Wu@....com.tw>
> 
> Reviewed-by: Pin-yen Lin <treapking@...omium.org>

For the sake of somebody applying the patch because it was R-B'ed

Nacked-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>

The commit message doesn't describe what is being done and why, it
doesn't have Fixes tags, etc.

Hermes, I'm not sure what's happening on your side. I have seen several
revisions of this patch with minimal modifications (and being a part of
different series). Some of them were marked as v1 (although you've sent
different patches as v1), other had v2 (but no changelog, etc). Please
adhere to the described process of sending patches.

-- 
With best wishes
Dmitry