| Message ID | 20231211205920.698939-1-b-brnich@ti.com |
|---|---|
| Headers | show |
| Series | Update Wave521c Compatible for TI Devices | expand |
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
Hi Brandon, On 28/12/2023 16:00, Brnich, Brandon wrote: > 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? This will have to be a 'fixes' pull request for v6.8 once v6.8-rc1 is released. These patches came in too late to make it into our staging tree. (Christmas vacation...) Keep an eye out for this, if it is not in rc3/rc4, then ping me and Sebastian. Regards, Hans > > [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 >