From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Dan Murphy <dmurphy@ti.com>, linux-doc@vger.kernel.org
Cc: devicetree@vger.kernel.org, netdev@vger.kernel.org,
linux-can@vger.kernel.org, robh+dt@kernel.org,
davem@davemloft.net, wg@grandegger.com, corbet@lwn.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: dt: Fix m_can.txt reference in tcan4x5x.txt
Date: Wed, 18 Mar 2020 11:36:50 +0100 [thread overview]
Message-ID: <8a450951-a28d-dabf-6d52-2c827c5b749e@pengutronix.de> (raw)
In-Reply-To: <20200317161900.14380-1-dmurphy@ti.com>
On 3/17/20 5:19 PM, Dan Murphy wrote:
> Fix the m_can.txt reference to point to the bosch,m_can.yaml.
>
> Fixes: 824674b59f72 ("dt-bindings: net: can: Convert M_CAN to json-schema")
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
Mauro Carvalho Chehab has already send a patch. See:
https://lkml.org/lkml/2020/3/17/843
Feel free to ack that patch.
Marc
> ---
> Documentation/devicetree/bindings/net/can/tcan4x5x.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/net/can/tcan4x5x.txt b/Documentation/devicetree/bindings/net/can/tcan4x5x.txt
> index 6bdcc3f84bd3..3613c2c8f75d 100644
> --- a/Documentation/devicetree/bindings/net/can/tcan4x5x.txt
> +++ b/Documentation/devicetree/bindings/net/can/tcan4x5x.txt
> @@ -14,7 +14,7 @@ Required properties:
> the interrupt.
> - interrupts: interrupt specification for data-ready.
>
> -See Documentation/devicetree/bindings/net/can/m_can.txt for additional
> +See Documentation/devicetree/bindings/net/can/bosch,m_can.yaml for additional
> required property details.
>
> Optional properties:
>
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2020-03-18 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 16:19 [PATCH] docs: dt: Fix m_can.txt reference in tcan4x5x.txt Dan Murphy
2020-03-18 10:36 ` Marc Kleine-Budde [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=8a450951-a28d-dabf-6d52-2c827c5b749e@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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).