From: Pavel Machek <pavel@ucw.cz>
To: pisa@cmp.felk.cvut.cz
Cc: linux-can@vger.kernel.org, devicetree@vger.kernel.org,
mkl@pengutronix.de, socketcan@hartkopp.net, wg@grandegger.com,
davem@davemloft.net, robh+dt@kernel.org, mark.rutland@arm.com,
c.emde@osadl.org, armbru@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, martin.jerabek01@gmail.com,
ondrej.ille@gmail.com, jnovak@fel.cvut.cz, jara.beran@gmail.com,
porazil@pikron.com
Subject: Re: [PATCH v4 2/6] dt-bindings: net: can: binding for CTU CAN FD open-source IP core.
Date: Tue, 4 Aug 2020 11:20:21 +0200 [thread overview]
Message-ID: <20200804092021.yd3wisz3g2ed6ioe@duo.ucw.cz> (raw)
In-Reply-To: <20200804091817.yuf6s26bclehpwwi@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
On Tue 2020-08-04 11:18:17, Pavel Machek wrote:
> Hi!
>
> > The commit text again to make checkpatch happy.
>
> ?
>
>
> > + oneOf:
> > + - items:
> > + - const: ctu,ctucanfd
> > + - const: ctu,canfd-2
> > + - const: ctu,ctucanfd
>
> For consistency, can we have ctu,canfd-1, ctu,canfd-2?
Make it ctu,ctucanfd-1, ctu,ctucanfd-2... to make it consistent with
the file names.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-08-04 9:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 18:34 [PATCH v4 0/6] CTU CAN FD open-source IP core SocketCAN driver, PCI, platform integration and documentation pisa
2020-08-03 18:34 ` [PATCH v4 1/6] dt-bindings: vendor-prefix: add prefix for the Czech Technical University in Prague pisa
2020-08-03 18:34 ` [PATCH v4 2/6] dt-bindings: net: can: binding for CTU CAN FD open-source IP core pisa
2020-08-04 9:18 ` Pavel Machek
2020-08-04 9:20 ` Pavel Machek [this message]
2020-08-06 14:47 ` Rob Herring
2020-08-06 15:53 ` Pavel Pisa
2020-08-06 14:43 ` Rob Herring
2020-08-03 18:34 ` [PATCH v4 3/6] can: ctucanfd: add support for CTU CAN FD open-source IP core - bus independent part pisa
2020-08-04 9:57 ` Pavel Machek
2020-08-03 18:34 ` [PATCH v4 4/6] can: ctucanfd: CTU CAN FD open-source IP core - PCI bus support pisa
2020-08-03 19:32 ` Randy Dunlap
2020-08-03 18:34 ` [PATCH v4 5/6] can: ctucanfd: CTU CAN FD open-source IP core - platform/SoC support pisa
2020-08-03 18:34 ` [PATCH v4 6/6] docs: ctucanfd: CTU CAN FD open-source IP core documentation pisa
2020-08-03 20:29 ` [PATCH v4 0/6] CTU CAN FD open-source IP core SocketCAN driver, PCI, platform integration and documentation Jakub Kicinski
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=20200804092021.yd3wisz3g2ed6ioe@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=armbru@redhat.com \
--cc=c.emde@osadl.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jara.beran@gmail.com \
--cc=jnovak@fel.cvut.cz \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.jerabek01@gmail.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=ondrej.ille@gmail.com \
--cc=pisa@cmp.felk.cvut.cz \
--cc=porazil@pikron.com \
--cc=robh+dt@kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
/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).