From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 3/3] dt-bindings: usb: add documentation for aspeed udc
Date: Mon, 16 May 2022 07:54:03 +0200 [thread overview]
Message-ID: <3499cca2-1d7b-12f5-adbe-0c9b279cc51a@linaro.org> (raw)
In-Reply-To: <HK0PR06MB32020539063F8A7C5D56E0B980CF9@HK0PR06MB3202.apcprd06.prod.outlook.com>
On 16/05/2022 03:59, Neal Liu wrote:
>>> Okay, I could rename it for next patch if you preferred.
>>> But there are lots of yaml files which are not named as first compatible.
>>
>> Yes, I know, I quite likely I also produced such bindings, but a specific name is
>> rather preferred. Otherwise you will have a difficult naming choice when your
>> next Aspeed UDC requires new bindings file because of some differences (not
>> yet known now).
>>
> We can rename the bindings if next Aspeed UDC needs, don't you think?
> Currently, Aspeed has no requirement.
So just use proper name from the beginning....
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-05-16 5:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 6:57 [PATCH 0/3] add Aspeed udc driver for ast2600 Neal Liu
2022-05-13 6:57 ` [PATCH 1/3] usb: gadget: add Aspeed ast2600 udc driver Neal Liu
2022-05-13 11:03 ` kernel test robot
2022-05-16 10:21 ` kernel test robot
2022-05-16 10:21 ` kernel test robot
2022-05-16 18:28 ` kernel test robot
2022-05-13 6:57 ` [PATCH 2/3] ARM: dts: aspeed: Add USB2.0 device controller node Neal Liu
2022-05-13 6:57 ` [PATCH 3/3] dt-bindings: usb: add documentation for aspeed udc Neal Liu
2022-05-13 9:07 ` Krzysztof Kozlowski
2022-05-13 15:39 ` Neal Liu
2022-05-14 20:21 ` Krzysztof Kozlowski
2022-05-16 1:59 ` Neal Liu
2022-05-16 5:54 ` Krzysztof Kozlowski [this message]
2022-05-16 6:00 ` Neal Liu
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=3499cca2-1d7b-12f5-adbe-0c9b279cc51a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=linux-aspeed@lists.ozlabs.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).