From: Naveen Krishna Ch <naveenkrishna.ch@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Naveen Krishna Chatradhi <nchatrad@amd.com>, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v4 2/3] hwmon: (amd_energy) Add documentation
Date: Sat, 25 Apr 2020 22:19:27 +0530 [thread overview]
Message-ID: <CAHfPSqC2b3Wj4GR0FuE2j55foAj=mZ1pCerRuC=BF0AG3FWbzw@mail.gmail.com> (raw)
In-Reply-To: <20200425154112.GA2170@roeck-us.net>
Hi Guenter
On Sat, 25 Apr 2020 at 21:11, Guenter Roeck <linux@roeck-us.net> wrote:
>
> On Fri, Apr 24, 2020 at 08:50:55AM +0530, Naveen Krishna Chatradhi wrote:
> > Document amd_energy driver with all chips supported by it.
> >
> > Cc: Guenter Roeck <linux@roeck-us.net>
> > Signed-off-by: Naveen Krishna Chatradhi <nchatrad@amd.com>
> > ---
> > Changes in v4:
> > None
>
> Still:
>
> /home/groeck/src/linux-stable/Documentation/hwmon/amd_energy.rst:36: WARNING: Unexpected indentation.
> /home/groeck/src/linux-stable/Documentation/hwmon/amd_energy.rst:40: WARNING: Unexpected indentation.
> /home/groeck/src/linux-stable/Documentation/hwmon/amd_energy.rst:44: WARNING: Unexpected indentation.
>
> Please run something like 'make SPHINXDIRS=hwmon htmldocs' and make sure
> it doesn't report any warnings.
My bad, I was not aware of the indentation in the Documentation.
I could Identify the issue. Thank you for the tip, will keep this in mind.
>
> Thanks,
> Guenter
--
Shine bright,
(: Nav :)
next prev parent reply other threads:[~2020-04-25 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 15:41 [PATCH v4 2/3] hwmon: (amd_energy) Add documentation Guenter Roeck
2020-04-25 16:49 ` Naveen Krishna Ch [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-24 3:20 [PATCH v4 1/3] hwmon: Add amd_energy driver to report energy counters Naveen Krishna Chatradhi
2020-04-24 3:20 ` [PATCH v4 2/3] hwmon: (amd_energy) Add documentation Naveen Krishna Chatradhi
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='CAHfPSqC2b3Wj4GR0FuE2j55foAj=mZ1pCerRuC=BF0AG3FWbzw@mail.gmail.com' \
--to=naveenkrishna.ch@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nchatrad@amd.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).