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: <4dba82cd7e264356ad66cf230c61dd89@ti.com>
Date: Thu, 28 Dec 2023 15:00:30 +0000
From: "Brnich, Brandon" <b-brnich@...com>
To: "linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Mauro
 Carvalho Chehab" <mchehab@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley
	<conor+dt@...nel.org>,
        Nas Chung <nas.chung@...psnmedia.com>,
        Jackson Lee
	<jackson.lee@...psnmedia.com>,
        Hans Verkuil <hverkuil-cisco@...all.nl>,
        Sebastian Fricke <sebastian.fricke@...labora.com>,
        Dafna Hirschfeld
	<dafna.hirschfeld@...labora.com>,
        Robert Beckett <bob.beckett@...labora.com>,
        Nicolas Dufresne <nicolas.dufresne@...labora.com>,
        Geert Uytterhoeven
	<geert@...ux-m68k.org>
CC: "Menon, Nishanth" <nm@...com>, "Etheridge, Darren" <detheridge@...com>
Subject: RE: [PATCH v3 0/2] Update Wave521c Compatible for TI Devices

Hello,

> -----Original Message-----
> Subject: [PATCH v3 0/2] Update Wave521c Compatible for TI Devices
> 
> Hello All,
> 
> There has been ongoing discussion[1] surrounding the issue of having K3
> prefix included in the compatible for dt bindings. This series removes this
> prefix from both the device tree binding as well as the driver. Updating the
> binding will not break the ABI at this point as the driver is still only in linux-
> next.

I noticed this series has still not made it in linux-next. I assume this is because
I improperly dropped the tags on the second patch [0] in the series between v2
and v3. This series should only be applied before bindings make it into release,
or the ABI breaks. Should I resend the series picking up proper tags this time?
Or is it too late for 6.8 at this point?

[0] https://patchwork.kernel.org/project/linux-media/patch/20231211205920.698939-3-b-brnich@ti.com/

> 
> Changes in v3:
> - Update example in dt bindings to match new compatible
> 
> Changes in v2:
> - Include more context surrounding patch
> - Fix style issues addressed by Krzysztof
> 
> [1] https://lore.kernel.org/all/20231201063309.tingjc3cjhsqb6r7@confusing/
> 
> 
> Brandon Brnich (2):
>   dt-bindings: media: Remove K3 Family Prefix from Compatible
>   media: chips-media: wave5: Remove K3 References
> 
>  Documentation/devicetree/bindings/media/cnm,wave521c.yaml | 4 ++--
>  drivers/media/platform/chips-media/wave5/wave5-vpu.c      | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> --
> 2.34.1

Thanks,

Brandon Brnich


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ