| Message ID | 87sexb3yfo.wl-kuninori.morimoto.gx@renesas.com |
|---|---|
| Headers | show |
| Series | ASoC: dt-bindings: rename akXXXX to asahi-kasei,akXXXX | expand |
On 18/06/2024 02:08, Kuninori Morimoto wrote: > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> > --- > .../bindings/sound/{ak4118.txt => asahi-kasei,ak4118.txt} | 0 > 1 file changed, 0 insertions(+), 0 deletions(-) > rename Documentation/devicetree/bindings/sound/{ak4118.txt => asahi-kasei,ak4118.txt} (100%) No need to rename TXT files. This just causes conflicts. Best regards, Krzysztof
Hi Mark > Kuninori Morimoto (5): > ASoC: dt-bindings: rename ak4118.txt to asahi-kasei,ak4118.txt > ASoC: dt-bindings: rename ak5386.txt to asahi-kasei,ak5386.txt > ASoC: dt-bindings: rename ak4375.yaml to asahi-kasei,ak4375.yaml > ASoC: dt-bindings: rename ak4613.yaml to asahi-kasei,ak4613.yaml > ASoC: dt-bindings: rename ak4642.yaml to asahi-kasei,ak4642.yaml As Krzysztof mentioned, [1/5][2/5] can be ignored, but should I send v2 patch for it ? And as Krzysztof mentioned, indeed there are some yamls which doesn't have vendor prefix. I can do some things for them, but I think it can be other patch-set, but is it OK ? Thank you for your help !! Best regards --- Kuninori Morimoto
On 19/06/2024 01:50, Kuninori Morimoto wrote: > > Hi Mark > >> Kuninori Morimoto (5): >> ASoC: dt-bindings: rename ak4118.txt to asahi-kasei,ak4118.txt >> ASoC: dt-bindings: rename ak5386.txt to asahi-kasei,ak5386.txt >> ASoC: dt-bindings: rename ak4375.yaml to asahi-kasei,ak4375.yaml >> ASoC: dt-bindings: rename ak4613.yaml to asahi-kasei,ak4613.yaml >> ASoC: dt-bindings: rename ak4642.yaml to asahi-kasei,ak4642.yaml > > As Krzysztof mentioned, [1/5][2/5] can be ignored, but should I send > v2 patch for it ? > > And as Krzysztof mentioned, indeed there are some yamls which doesn't have > vendor prefix. I can do some things for them, but I think it can be other > patch-set, but is it OK ? For me, renaming YAML files is mostly churn (messes with git log /requires -M/, might affect backporting), but if you want then correct all ASoC bindings in one patch. There is really no benefit in having 20 separate renames. Best regards, Krzysztof
Hi Mark Cc Rob, Krzysztof. These patches adds vendor prefix to asahi-kasei Kuninori Morimoto (5): ASoC: dt-bindings: rename ak4118.txt to asahi-kasei,ak4118.txt ASoC: dt-bindings: rename ak5386.txt to asahi-kasei,ak5386.txt ASoC: dt-bindings: rename ak4375.yaml to asahi-kasei,ak4375.yaml ASoC: dt-bindings: rename ak4613.yaml to asahi-kasei,ak4613.yaml ASoC: dt-bindings: rename ak4642.yaml to asahi-kasei,ak4642.yaml .../bindings/sound/{ak4118.txt => asahi-kasei,ak4118.txt} | 0 .../bindings/sound/{ak4375.yaml => asahi-kasei,ak4375.yaml} | 2 +- .../bindings/sound/{ak4613.yaml => asahi-kasei,ak4613.yaml} | 2 +- .../bindings/sound/{ak4642.yaml => asahi-kasei,ak4642.yaml} | 2 +- .../bindings/sound/{ak5386.txt => asahi-kasei,ak5386.txt} | 0 5 files changed, 3 insertions(+), 3 deletions(-) rename Documentation/devicetree/bindings/sound/{ak4118.txt => asahi-kasei,ak4118.txt} (100%) rename Documentation/devicetree/bindings/sound/{ak4375.yaml => asahi-kasei,ak4375.yaml} (94%) rename Documentation/devicetree/bindings/sound/{ak4613.yaml => asahi-kasei,ak4613.yaml} (94%) rename Documentation/devicetree/bindings/sound/{ak4642.yaml => asahi-kasei,ak4642.yaml} (94%) rename Documentation/devicetree/bindings/sound/{ak5386.txt => asahi-kasei,ak5386.txt} (100%)