devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Jiri Kosina <trivial@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: marvell,mmp2: fix a typo in bindings doc
Date: Wed, 19 Dec 2018 11:19:45 -0600	[thread overview]
Message-ID: <20181219171945.GA32656@bogus> (raw)
In-Reply-To: <20181203114748.637314-1-lkundrak@v3.sk>

On Mon, Dec 03, 2018 at 12:47:48PM +0100, Lubomir Rintel wrote:
> A trivial one, but it's annoying that copy & paste of the link
> doesn't work.
> 
> Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
> ---
>  Documentation/devicetree/bindings/clock/marvell,mmp2.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/clock/marvell,mmp2.txt b/Documentation/devicetree/bindings/clock/marvell,mmp2.txt
> index af376a01f2b7..b0447d9896bc 100644
> --- a/Documentation/devicetree/bindings/clock/marvell,mmp2.txt
> +++ b/Documentation/devicetree/bindings/clock/marvell,mmp2.txt
> @@ -18,4 +18,4 @@ Required Properties:
>  Each clock is assigned an identifier and client nodes use this identifier
>  to specify the clock which they consume.
>  
> -All these identifier could be found in <dt-bindings/clock/marvell-mmp2.h>.
> +All these identifier could be found in <dt-bindings/clock/marvell,mmp2.h>.

Really, should be: identifiers can be

> -- 
> 2.19.1
> 

      reply	other threads:[~2018-12-19 17:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 11:47 [PATCH] dt-bindings: marvell,mmp2: fix a typo in bindings doc Lubomir Rintel
2018-12-19 17:19 ` 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=20181219171945.GA32656@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --cc=mark.rutland@arm.com \
    --cc=trivial@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).