[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=VEC=GzkDfaOqauBB5Y79teS1ENA5wFUHZmnTRkg6Z4tg@mail.gmail.com>
Date: Thu, 17 Nov 2022 07:57:41 -0800
From: Doug Anderson <dianders@...omium.org>
To: Hsin-Yi Wang <hsinyi@...omium.org>
Cc: Sean Paul <seanpaul@...omium.org>,
Robert Foss <robert.foss@...aro.org>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Daniel Vetter <daniel@...ll.ch>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Allen Chen <allen.chen@....com.tw>,
David Airlie <airlied@...il.com>
Subject: Re: [PATCH v6 1/3] drm_bridge: register content protect property
Hi,
On Thu, Nov 17, 2022 at 3:08 AM Hsin-Yi Wang <hsinyi@...omium.org> wrote:
>
> Some bridges are able to update HDCP status from userspace request if
> they support HDCP.
>
> HDCP property is the same as other connector properties that needs to be
> created after the connecter is initialized and before the connector is
> registered.
>
> If there exists a bridge that supports HDCP, add the property to the
> bridge connector.
>
> Signed-off-by: Hsin-Yi Wang <hsinyi@...omium.org>
> Reviewed-by: Sean Paul <seanpaul@...omium.org>
> Reported-by: kernel test robot <lkp@...el.com>
Not sure it's worth spinning for, but FWIW I wouldn't put
"Reported-by: kernel test robot <lkp@...el.com>". The emails from that
bot are always a bit confusing in this regards, but I think they mean
"if the patch has already landed and you're sending a separate patch
with a fix then please add the "Reported-by" tag". ...but adding it to
the original patch just doesn't make a lot of sense.
Powered by blists - more mailing lists