From: Rob Herring <robh@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net,
robh+dt@kernel.org, mark.rutland@arm.com,
sriram.dash@samsung.com, linux-can@vger.kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: Re: [PATCH v4 2/2] dt-bindings: net: can: Convert M_CAN to json-schema
Date: Tue, 18 Feb 2020 15:11:38 -0600 [thread overview]
Message-ID: <20200218211138.GA12217@bogus> (raw)
In-Reply-To: <20200207100306.20997-3-benjamin.gaignard@st.com>
On Fri, 7 Feb 2020 11:03:06 +0100, Benjamin Gaignard wrote:
> Convert M_CAN bindings to json-schema
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> version 4:
> - remove useless ref to can-transceiver.yaml
>
> version 3:
> - move can-transceive node into bosch,m_can.yaml bindings
> .../devicetree/bindings/net/can/bosch,m_can.yaml | 144 +++++++++++++++++++++
> .../devicetree/bindings/net/can/m_can.txt | 75 -----------
> 2 files changed, 144 insertions(+), 75 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt
>
Applied, thanks.
Rob
prev parent reply other threads:[~2020-02-18 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 10:03 [PATCH v4 0/2] Convert bosch,m_can to json-schema Benjamin Gaignard
2020-02-07 10:03 ` [PATCH v4 1/2] dt-bindinsg: net: can: Convert can-transceiver " Benjamin Gaignard
2020-02-18 21:11 ` Rob Herring
2020-02-07 10:03 ` [PATCH v4 2/2] dt-bindings: net: can: Convert M_CAN " Benjamin Gaignard
2020-02-18 21:11 ` Rob Herring [this message]
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=20200218211138.GA12217@bogus \
--to=robh@kernel.org \
--cc=benjamin.gaignard@st.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sriram.dash@samsung.com \
--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).