linux-kernel - Re: [PATCH v10 1/3] media: dt-bindings: media: add bindings for Rockchip CIF

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] [day] [month] [year] [list]

Message-ID: <20231115-angles-entrust-f72112053ee0@squawk>
Date:   Wed, 15 Nov 2023 20:16:43 +0000
From:   Conor Dooley <conor@...nel.org>
To:     Paul Kocialkowski <paul.kocialkowski@...tlin.com>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Mehdi Djait <mehdi.djait@...tlin.com>, mchehab@...nel.org,
        heiko@...ech.de, hverkuil-cisco@...all.nl,
        krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org,
        conor+dt@...nel.org, linux-media@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        thomas.petazzoni@...tlin.com, alexandre.belloni@...tlin.com,
        maxime.chevallier@...tlin.com, michael.riesch@...fvision.net
Subject: Re: [PATCH v10 1/3] media: dt-bindings: media: add bindings for
 Rockchip CIF

On Wed, Nov 15, 2023 at 04:07:07PM +0100, Paul Kocialkowski wrote:
> Hi,
> 
> On Tue 14 Nov 23, 17:51, Conor Dooley wrote:
> > On Mon, Nov 13, 2023 at 05:54:08PM +0100, Paul Kocialkowski wrote:
> >  
> > > > Ultimately, I don't care what the file ends up being called when there
> > > > are multiple devices documented in it. I'd ack a patch renaming to the
> > > > œriginal incarnation of the IP when the documentation for that IP is
> > > > added without a second thought.
> > > 
> > > That would be agreeable to me if my proposal still ends up feeling unreasonable
> > > to you. But I might very well take you at your word since I ended up purchasing
> > > a RK3066 board in a moment of weakness last week.
> > 
> > The ideal outcome I suppose would be documenting both variants. If
> > you've gone ahead and bought one, give that a go.
> 
> Yeah I'll try to do that eventually, but we really want to have this series
> merged as soon as possible. So it wouldn't be reasonable for us to wait for
> RK3066 support.
> 
> What's your final decision for now: is it okay to keep the file named
> rockchip,rk3066-cif.yaml (without this compatible in the file) or do you still
> want it called rockchip,px30-vip.yaml?

I'd still rather it was called after the only compatible in the file and
subsequently renamed, sorry.

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)