From: Rob Herring <robh@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Gerhard Bertelsmann <info@gerhard-bertelsmann.de>,
devicetree@vger.kernel.org, linux-can@vger.kernel.org,
Evgeny Boger <boger@wirenboard.com>
Subject: Re: [PATCH net-next 2/4] dt-binding: can: sun4i_can: include common CAN controller bindings
Date: Tue, 8 Feb 2022 21:13:10 -0600 [thread overview]
Message-ID: <YgMxRuZOzXKvdBgN@robh.at.kernel.org> (raw)
In-Reply-To: <20220124220653.3477172-3-mkl@pengutronix.de>
On Mon, 24 Jan 2022 23:06:51 +0100, Marc Kleine-Budde wrote:
> Since commit
>
> | 1f9234401ce0 ("dt-bindings: can: add can-controller.yaml")
>
> there is a common CAN controller binding. Add this to the sun4i_can
> binding.
>
> Cc: Evgeny Boger <boger@wirenboard.com>
> Cc: Gerhard Bertelsmann <info@gerhard-bertelsmann.de>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
> .../devicetree/bindings/net/can/allwinner,sun4i-a10-can.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-09 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 22:06 [PATCH net-next 0/4] dt-binding: can: add common CAN controller bindings to existing CAN driver bindings Marc Kleine-Budde
2022-01-24 22:06 ` [PATCH net-next 1/4] dt-binding: can: mcp251xfd: include common CAN controller bindings Marc Kleine-Budde
2022-02-09 3:12 ` Rob Herring
2022-01-24 22:06 ` [PATCH net-next 2/4] dt-binding: can: sun4i_can: " Marc Kleine-Budde
2022-02-09 3:13 ` Rob Herring [this message]
2022-01-24 22:06 ` [PATCH net-next 3/4] dt-binding: can: m_can: " Marc Kleine-Budde
2022-02-09 3:13 ` Rob Herring
2022-01-24 22:06 ` [PATCH net-next 4/4] dt-binding: can: rcar-can: " Marc Kleine-Budde
2022-01-25 4:14 ` Rob Herring
2022-01-25 7:55 ` Marc Kleine-Budde
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=YgMxRuZOzXKvdBgN@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=boger@wirenboard.com \
--cc=devicetree@vger.kernel.org \
--cc=info@gerhard-bertelsmann.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=robh+dt@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).