linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: yegorslists@googlemail.com
Cc: linux-kernel@vger.kernel.org, p.zabel@pengutronix.de,
	devicetree@vger.kernel.org, mark.rutland@arm.com
Subject: Re: [PATCH] Documentation: ti-syscon-reset: fix header path
Date: Mon, 12 Dec 2016 12:40:21 -0600	[thread overview]
Message-ID: <20161212184021.hewybkfaygrle63a@rob-hp-laptop> (raw)
In-Reply-To: <1481278287-23842-1-git-send-email-yegorslists@googlemail.com>

On Fri, Dec 09, 2016 at 11:11:27AM +0100, yegorslists@googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> 
> 'include' was missing from path.
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
>  Documentation/devicetree/bindings/reset/ti-syscon-reset.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/reset/ti-syscon-reset.txt b/Documentation/devicetree/bindings/reset/ti-syscon-reset.txt
> index 164c7f3..5b20e20 100644
> --- a/Documentation/devicetree/bindings/reset/ti-syscon-reset.txt
> +++ b/Documentation/devicetree/bindings/reset/ti-syscon-reset.txt
> @@ -44,7 +44,7 @@ Required properties:
>  			              reset status register
>  			    Cell #7 : Flags used to control reset behavior,
>  			              availible flags defined in the DT include
> -			              file <dt-bindings/reset/ti-syscon.h>
> +			              file <include/dt-bindings/reset/ti-syscon.h>

There's pretty much equal mixture of include or not. Not really much 
point in fixing 1 instance if there's no clear correct way. Given it is 
written with <...>, that matches how you write the include statement.

Rob

  reply	other threads:[~2016-12-12 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09 10:11 [PATCH] Documentation: ti-syscon-reset: fix header path yegorslists
2016-12-12 18:40 ` Rob Herring [this message]
2016-12-12 19:52   ` Yegor Yefremov

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=20161212184021.hewybkfaygrle63a@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=p.zabel@pengutronix.de \
    --cc=yegorslists@googlemail.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).