From: Vinod Koul <vkoul@kernel.org>
To: Changbin Du <changbin.du@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Amit Daniel Kachhap <amit.kachhap@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Javi Merino <javi.merino@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: Fix build error for cpu-idle-cooling.rst and client.rst
Date: Mon, 3 Feb 2020 20:52:55 +0530 [thread overview]
Message-ID: <20200203152255.GQ2841@vkoul-mobl> (raw)
In-Reply-To: <20200203140223.10298-1-changbin.du@gmail.com>
On 03-02-20, 22:02, Changbin Du wrote:
> This fixed some errors and warnings in cpu-idle-cooling.rst and client.rst.
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage: ...Documentation/driver-api/thermal/cpu-idle-cooling.rst:96: (SEVERE/4) Unexpected section title.
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage: ...Documentation/driver-api/dmaengine/client.rst:155: (SEVERE/4) Unexpected section title.
>
> Signed-off-by: Changbin Du <changbin.du@gmail.com>
>
> ---
> v2: rebase.
> ---
> Documentation/driver-api/dmaengine/client.rst | 14 +++++++---
> .../driver-api/thermal/cpu-idle-cooling.rst | 27 ++++++++++---------
> Documentation/driver-api/thermal/index.rst | 1 +
> 3 files changed, 26 insertions(+), 16 deletions(-)
>
> diff --git a/Documentation/driver-api/dmaengine/client.rst b/Documentation/driver-api/dmaengine/client.rst
> index a9a7a3c84c63..2104830a99ae 100644
> --- a/Documentation/driver-api/dmaengine/client.rst
> +++ b/Documentation/driver-api/dmaengine/client.rst
> @@ -151,8 +151,8 @@ The details of these operations are:
> Note that callbacks will always be invoked from the DMA
> engines tasklet, never from interrupt context.
>
> - Optional: per descriptor metadata
> - ---------------------------------
> + **Optional: per descriptor metadata**
I have already fixed it up and it is linux-next (thru dmaengine tree)
Can you please send rest of client.rst changes to me as well
Thanks
--
~Vinod
next prev parent reply other threads:[~2020-02-03 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 14:02 [PATCH v2] Documentation: Fix build error for cpu-idle-cooling.rst and client.rst Changbin Du
2020-02-03 15:22 ` Vinod Koul [this message]
2020-02-04 12:43 ` Changbin Du
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=20200203152255.GQ2841@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=amit.kachhap@gmail.com \
--cc=changbin.du@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=javi.merino@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=viresh.kumar@linaro.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