Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Jean Delvare" <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: hwmon: Fix incorrect $id paths
Date: Thu, 9 Apr 2020 13:33:14 -0700	[thread overview]
Message-ID: <20200409203314.GB143353@roeck-us.net> (raw)
In-Reply-To: <20200409202516.25282-1-robh@kernel.org>

On Thu, Apr 09, 2020 at 02:25:15PM -0600, Rob Herring wrote:
> Fix the path warnings in the adi,axi-fan-control and adt7475 bindings:
> 
> Documentation/devicetree/bindings/hwmon/adt7475.yaml: $id:
>   relative path/filename doesn't match actual path or filename
>   expected: http://devicetree.org/schemas/hwmon/adt7475.yaml#
> Documentation/devicetree/bindings/hwmon/adi,axi-fan-control.yaml: $id:
>   relative path/filename doesn't match actual path or filename
>   expected: http://devicetree.org/schemas/hwmon/adi,axi-fan-control.yaml#
> 
> Cc: "Nuno Sá" <nuno.sa@analog.com>
> Cc: Jean Delvare <jdelvare@suse.com>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: linux-hwmon@vger.kernel.org
> Signed-off-by: Rob Herring <robh@kernel.org>

Acked-by: Guenter Roeck <linux@roeck-us.net>

> ---
> Will take this via the DT tree.
> 
> Rob
> 
>  .../devicetree/bindings/hwmon/adi,axi-fan-control.yaml          | 2 +-
>  Documentation/devicetree/bindings/hwmon/adt7475.yaml            | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/hwmon/adi,axi-fan-control.yaml b/Documentation/devicetree/bindings/hwmon/adi,axi-fan-control.yaml
> index 29bb2c778c59..7db78767c02d 100644
> --- a/Documentation/devicetree/bindings/hwmon/adi,axi-fan-control.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/adi,axi-fan-control.yaml
> @@ -2,7 +2,7 @@
>  # Copyright 2019 Analog Devices Inc.
>  %YAML 1.2
>  ---
> -$id: http://devicetree.org/schemas/bindings/hwmon/adi,axi-fan-control.yaml#
> +$id: http://devicetree.org/schemas/hwmon/adi,axi-fan-control.yaml#
>  $schema: http://devicetree.org/meta-schemas/core.yaml#
>  
>  title: Analog Devices AXI FAN Control Device Tree Bindings
> diff --git a/Documentation/devicetree/bindings/hwmon/adt7475.yaml b/Documentation/devicetree/bindings/hwmon/adt7475.yaml
> index 76985034ea73..46c441574f98 100644
> --- a/Documentation/devicetree/bindings/hwmon/adt7475.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/adt7475.yaml
> @@ -1,7 +1,7 @@
>  # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>  %YAML 1.2
>  ---
> -$id: http://devicetree.org/schemas/adt7475.yaml#
> +$id: http://devicetree.org/schemas/hwmon/adt7475.yaml#
>  $schema: http://devicetree.org/meta-schemas/core.yaml#
>  
>  title: ADT7475 hwmon sensor
> -- 
> 2.20.1
> 

  reply	other threads:[~2020-04-09 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 20:25 [PATCH] dt-bindings: hwmon: Fix incorrect $id paths Rob Herring
2020-04-09 20:33 ` Guenter Roeck [this message]
2020-04-14  9:05 ` Sa, Nuno

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=20200409203314.GB143353@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@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