From: Rob Herring <robh@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Manivannan Sadhasivam <mani@kernel.org>,
Thomas Kopp <thomas.kopp@microchip.com>,
linux-can@vger.kernel.org
Subject: Re: [PATCH net-next 1/4] dt-binding: can: mcp251xfd: include common CAN controller bindings
Date: Tue, 8 Feb 2022 21:12:55 -0600 [thread overview]
Message-ID: <YgMxN5KPWllWLwJd@robh.at.kernel.org> (raw)
In-Reply-To: <20220124220653.3477172-2-mkl@pengutronix.de>
On Mon, 24 Jan 2022 23:06:50 +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 mcp251xfd
> binding.
>
> Cc: Manivannan Sadhasivam <mani@kernel.org>
> Cc: Thomas Kopp <thomas.kopp@microchip.com>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
> .../devicetree/bindings/net/can/microchip,mcp251xfd.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-09 3:13 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 [this message]
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
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=YgMxN5KPWllWLwJd@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mkl@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=thomas.kopp@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.