From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Nas Chung <nas.chung@chipsnmedia.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Jackson Lee <jackson.lee@chipsnmedia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
NXP Linux Team <linux-imx@nxp.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Conor Dooley <conor+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Robert Beckett <bob.beckett@collabora.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v12 6/7] dt-bindings: media: wave5: add yaml devicetree bindings
Date: Mon, 18 Sep 2023 22:14:44 +0200 [thread overview]
Message-ID: <7f5021c9-49a8-ad06-5a48-1d531dbda12e@linaro.org> (raw)
In-Reply-To: <7412a756ee4c83c62b3dc866b5a351e1bc4afa33.camel@collabora.com>
On 18/09/2023 21:16, Nicolas Dufresne wrote:
>>>>
>>>> A nit, subject: drop second/last, redundant "yaml devicetree indings".
>>>> The "dt-bindings" prefix is already stating that these are bindings.
>>>> Basically three words bringing zero information.
>>>
>>> Okay so:
>>> `dt-bindings: media: wave5: add devicetree`
>>
>> Still not, because devicetree is duplicating "dt". It's redundant.
>>
>> Instead should be (with correct order of prefixes):
>>
>> media: dt-bindings: wave5: add AzureWaveFooBar XYL ABC10 (whatever
>> company and full product name it is)
>
> So maybe this one ?
>
> media: dt-bindings: wave5: add Chips&Media 521c codec IP support
Sure, sounds good for me.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-18 20:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 21:11 [PATCH v12 0/7] Wave5 codec driver Sebastian Fricke
2023-09-15 21:11 ` [PATCH v12 1/7] media: v4l2: Add ignore_streaming flag Sebastian Fricke
2023-09-20 12:59 ` Hans Verkuil
2023-09-20 14:08 ` Nicolas Dufresne
2023-09-20 14:49 ` Hans Verkuil
2023-09-21 18:39 ` Nicolas Dufresne
2023-09-22 8:28 ` Hans Verkuil
2023-09-22 20:20 ` Nicolas Dufresne
2023-09-25 9:03 ` Hans Verkuil
2023-09-15 21:11 ` [PATCH v12 2/7] media: v4l2: Allow M2M job queuing w/o streaming CAP queue Sebastian Fricke
2023-09-15 21:11 ` [PATCH v12 3/7] media: platform: chips-media: Move Coda to separate folder Sebastian Fricke
2023-09-15 21:11 ` [PATCH v12 4/7] media: chips-media: wave5: Add vpuapi layer Sebastian Fricke
2023-09-25 11:35 ` Benjamin Gaignard
2023-09-15 21:11 ` [PATCH v12 5/7] media: chips-media: wave5: Add the v4l2 layer Sebastian Fricke
2023-09-15 21:22 ` Sebastian Fricke
2023-09-16 20:28 ` Ivan Bornyakov
2023-09-16 20:55 ` Ivan Bornyakov
2023-09-20 15:13 ` Hans Verkuil
2023-09-21 19:11 ` Nicolas Dufresne
2023-09-22 7:33 ` Hans Verkuil
2023-09-26 23:29 ` Nicolas Dufresne
2023-09-27 7:19 ` Hans Verkuil
2023-10-02 23:51 ` Deborah Brouwer
2023-10-03 6:54 ` Hans Verkuil
2023-09-15 21:11 ` [PATCH v12 6/7] dt-bindings: media: wave5: add yaml devicetree bindings Sebastian Fricke
2023-09-15 22:16 ` Rob Herring
2023-09-17 7:56 ` Krzysztof Kozlowski
2023-09-18 6:49 ` Sebastian Fricke
2023-09-18 12:02 ` Krzysztof Kozlowski
2023-09-18 19:16 ` Nicolas Dufresne
2023-09-18 20:14 ` Krzysztof Kozlowski [this message]
2023-09-15 21:11 ` [PATCH v12 7/7] media: chips-media: wave5: Add wave5 driver to maintainers file Sebastian Fricke
2023-09-20 13:02 ` Hans Verkuil
2023-09-20 15:32 ` Sebastian Fricke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7f5021c9-49a8-ad06-5a48-1d531dbda12e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bob.beckett@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=jackson.lee@chipsnmedia.com \
--cc=kernel@collabora.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nas.chung@chipsnmedia.com \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.fricke@collabora.com \
--cc=shawnguo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).