All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Nuno Sá" <nuno.sa@analog.com>
Cc: <linux-hwmon@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-doc@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Jean Delvare <jdelvare@suse.com>
Subject: Re: [PATCH v2 1/2] hwmon: Add support for ltc2947
Date: Fri, 11 Oct 2019 08:30:48 -0600	[thread overview]
Message-ID: <20191011083048.4fa39734@lwn.net> (raw)
In-Reply-To: <20191011114853.159327-1-nuno.sa@analog.com>

On Fri, 11 Oct 2019 13:48:52 +0200
Nuno Sá <nuno.sa@analog.com> wrote:

> The ltc2947 is a high precision power and energy monitor with an
> internal sense resistor supporting up to +/- 30A. Three internal no
> Latency ADCs ensure accurate measurement of voltage and current, while
> high-bandwidth analog multiplication of voltage and current provides
> accurate power measurement in a wide range of applications. Internal or
> external clocking options enable precise charge and energy measurements.
> 
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>

[...]

> diff --git a/Documentation/hwmon/ltc2947.rst b/Documentation/hwmon/ltc2947.rst
> new file mode 100644
> index 000000000000..05df19775fb3
> --- /dev/null
> +++ b/Documentation/hwmon/ltc2947.rst

So this file has a .rst extension, but it's not actually a restructured
text file.  It will add a bunch of warnings during the docs build.  The
good news is that fixing it up will not be hard; see Documention/doc-guide
if need be.

Thanks,

jon

  parent reply	other threads:[~2019-10-11 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 11:48 [PATCH v2 1/2] hwmon: Add support for ltc2947 Nuno Sá
2019-10-11 11:48 ` [PATCH v2 2/2] dt-bindings: hwmon: Add ltc2947 documentation Nuno Sá
2019-10-14 18:14   ` Rob Herring
2019-10-11 14:30 ` Jonathan Corbet [this message]
2019-10-20 16:21 ` [PATCH v2 1/2] hwmon: Add support for ltc2947 Guenter Roeck

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=20191011083048.4fa39734@lwn.net \
    --to=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=nuno.sa@analog.com \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.