From: Philipp Zabel <p.zabel@pengutronix.de>
To: Kaixu Xia <xiakaixu@huawei.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kaixu.xia@linaro.org
Subject: Re: [PATCH] Documentation: of: fix typo in graph bindings
Date: Mon, 05 Jan 2015 11:37:31 +0100 [thread overview]
Message-ID: <1420454251.3180.20.camel@pengutronix.de> (raw)
In-Reply-To: <1420452136-76466-1-git-send-email-xiakaixu@huawei.com>
Am Montag, den 05.01.2015, 18:02 +0800 schrieb Kaixu Xia:
> Just fix a minor typo about the example path.
>
> Signed-off-by: Kaixu Xia <xiakaixu@huawei.com>
Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
thanks
Philipp
> ---
> Documentation/devicetree/bindings/graph.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/graph.txt b/Documentation/devicetree/bindings/graph.txt
> index 1a69c07..fcb1c6a 100644
> --- a/Documentation/devicetree/bindings/graph.txt
> +++ b/Documentation/devicetree/bindings/graph.txt
> @@ -19,7 +19,7 @@ type of the connections, they just map their existence. Specific properties
> may be described by specialized bindings depending on the type of connection.
>
> To see how this binding applies to video pipelines, for example, see
> -Documentation/device-tree/bindings/media/video-interfaces.txt.
> +Documentation/devicetree/bindings/media/video-interfaces.txt.
> Here the ports describe data interfaces, and the links between them are
> the connecting data buses. A single port with multiple connections can
> correspond to multiple devices being connected to the same physical bus.
next prev parent reply other threads:[~2015-01-05 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 10:02 [PATCH] Documentation: of: fix typo in graph bindings Kaixu Xia
2015-01-05 10:37 ` Philipp Zabel [this message]
[not found] ` <1420452136-76466-1-git-send-email-xiakaixu-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-01-13 20:04 ` Rob Herring
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=1420454251.3180.20.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kaixu.xia@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=xiakaixu@huawei.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).