linux-kernel - Re: [PATCH v8 1/2] drm_bridge: register content protect property

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: <CAD=FV=WFR7b=7h6gnyH_MtLW-dcngEqocBz6Lox4_JSBMO9RhQ@mail.gmail.com>
Date: Wed, 20 Aug 2025 08:25:15 -0700
From: Doug Anderson <dianders@...omium.org>
To: Fei Shao <fshao@...omium.org>
Cc: Hubert Mazur <hmazur@...gle.com>, Sean Paul <seanpaul@...omium.org>, 
	Hsin-Yi Wang <hsinyi@...omium.org>, dri-devel@...ts.freedesktop.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 1/2] drm_bridge: register content protect property

Hi,

On Tue, Aug 12, 2025 at 8:01 PM Fei Shao <fshao@...omium.org> wrote:
>
> On Wed, Aug 13, 2025 at 2:07 AM Doug Anderson <dianders@...omium.org> wrote:
> >
> > Hi,
> >
> > On Tue, Aug 12, 2025 at 1:23 AM Fei Shao <fshao@...omium.org> wrote:
> > >
> > > From: Hsin-Yi Wang <hsinyi@...omium.org>
> > >
> > > Some bridges can update HDCP status based on userspace requests if they
> > > support HDCP.
> > >
> > > The HDCP property is created after connector initialization and before
> > > registration, just like other connector properties.
> > >
> > > Add the content protection property to the connector if a bridge
> > > supports HDCP.
> > >
> > > Signed-off-by: Hsin-Yi Wang <hsinyi@...omium.org>
> > > Signed-off-by: Fei Shao <fshao@...omium.org>
> > > Reviewed-by: Sean Paul <seanpaul@...omium.org>
> >
> > nit: your Signed-off-by should always be moved to the bottom when
> > posting patches. I wouldn't bother re-posting just for that, though...
>
> Ah sorry, I didn't notice that..
> Could you rearrange the tag order for me when applying these patches?

Sure, adjusted and pushed to drm-misc-next:

[1/2] drm_bridge: register content protect property
      commit: 407a2fab3c99c40ad1acedaf028e8222da1f0433