Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Felix Nieuwenhuizen <Felix.Nieuwenhuizen@etas.com>
Cc: linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] hwmon: (pmbus/ltc2978) add support for LTC7132 - docs
Date: Sun, 15 Jan 2023 08:15:47 -0800	[thread overview]
Message-ID: <20230115161547.GA1246825@roeck-us.net> (raw)
In-Reply-To: <20230105074900.5730-1-Felix.Nieuwenhuizen@etas.com>

On Thu, Jan 05, 2023 at 08:49:00AM +0100, Felix Nieuwenhuizen wrote:
> Add missing compatible string "lltc,ltc7132" to the bindings documentation.
> 
> Signed-off-by: Felix Nieuwenhuizen <Felix.Nieuwenhuizen@etas.com>

This needs to be reviewed by a DT maintainer. Please refer to
scripts/get_maintainer.pl to determine who needs to be copied.

Guenter

> ---
>  Documentation/devicetree/bindings/hwmon/ltc2978.txt | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/hwmon/ltc2978.txt b/Documentation/devicetree/bindings/hwmon/ltc2978.txt
> index 4e7f6215a453..61783b3819bf 100644
> --- a/Documentation/devicetree/bindings/hwmon/ltc2978.txt
> +++ b/Documentation/devicetree/bindings/hwmon/ltc2978.txt
> @@ -16,6 +16,7 @@ Required properties:
>    * "lltc,ltc3886"
>    * "lltc,ltc3887"
>    * "lltc,ltc3889"
> +  * "lltc,ltc7132"
>    * "lltc,ltc7880"
>    * "lltc,ltm2987"
>    * "lltc,ltm4664"

      reply	other threads:[~2023-01-15 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0221027133201.GA566451@roeck-us.net>
2022-10-27 14:51 ` [PATCH v2] hwmon: (pmbus/ltc2978) add support for LTC7132 Felix Nieuwenhuizen
2022-10-28 18:15   ` Guenter Roeck
2022-12-08  2:13   ` Rob Herring
2023-01-05  7:49     ` [PATCH] hwmon: (pmbus/ltc2978) add support for LTC7132 - docs Felix Nieuwenhuizen
2023-01-15 16:15       ` Guenter Roeck [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=20230115161547.GA1246825@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Felix.Nieuwenhuizen@etas.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --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