From: Randy Dunlap <rdunlap@infradead.org>
To: Changbin Du <changbin.du@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Vinod Koul <vkoul@kernel.org>,
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] Documentation: Fix build error for cpu-idle-cooling.rst and client.rst
Date: Sat, 1 Feb 2020 08:17:27 -0800 [thread overview]
Message-ID: <4ca88e39-7dcd-1709-96cc-4fb324715835@infradead.org> (raw)
In-Reply-To: <20200201125914.lpejzlgxazuu4i6f@mail.google.com>
On 2/1/20 4:59 AM, Changbin Du wrote:
> Hi,
> On Fri, Jan 31, 2020 at 10:33:30PM -0800, Randy Dunlap wrote:
>> On 1/31/20 10:25 PM, 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>
>>
>> Hi,
>> This commit has been merged:
>> commit fe27f13d677ccd826386094df6977cfbc13ccf5e
>> Author: Randy Dunlap <rdunlap@infradead.org>
>> Date: Mon Jan 20 14:33:16 2020 -0800
>>
>> Documentation: cpu-idle-cooling: fix a SEVERE docs build failure
>>
>> Feel free to send patches against current Linus git tree.
>>
> Seems it is not in Linus's tree yet. But is it in Jonathan's tree now? I could
> rebase to the doc tree instead.
>
>> Thanks.
Hm, now I am confused. I cannot find it at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
but in my local clone of that git tree, I can do
$ git show fe27f13d677ccd826386094df6977cfbc13ccf5e
and see it.
--
~Randy
next prev parent reply other threads:[~2020-02-01 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 6:25 Changbin Du
2020-02-01 6:33 ` Randy Dunlap
2020-02-01 12:59 ` Changbin Du
2020-02-01 16:17 ` Randy Dunlap [this message]
2020-02-03 14:05 ` 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=4ca88e39-7dcd-1709-96cc-4fb324715835@infradead.org \
--to=rdunlap@infradead.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 \
--cc=vkoul@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
all inboxes | Powered by JetHome®