From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Vinod Koul <vkoul@kernel.org>, Michael Ellerman <mpe@ellerman.id.au>
Cc: dma <dmaengine@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, <corbet@lwn.net>,
<linux-doc@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Docs build broken by driver-api/dmaengine/client.rst ? (was Re: [GIT PULL]: dmaengine updates for v5.6-rc1)
Date: Tue, 28 Jan 2020 14:35:17 +0200 [thread overview]
Message-ID: <f88ed09c-6244-71e5-3be4-b733ee348b79@ti.com> (raw)
In-Reply-To: <20200128122415.GU2841@vkoul-mobl>
Hi Michael, Vinod,
On 28/01/2020 14.24, Vinod Koul wrote:
> Hi Michael,
>
> On 28-01-20, 22:50, Michael Ellerman wrote:
>> Hi Vinod,
>>
>> Vinod Koul <vkoul@kernel.org> writes:
>>> Hello Linus,
>>>
>>> Please pull to receive the dmaengine updates for v5.6-rc1. This time we
>>> have a bunch of core changes to support dynamic channels, hotplug of
>>> controllers, new apis for metadata ops etc along with new drivers for
>>> Intel data accelerators, TI K3 UDMA, PLX DMA engine and hisilicon
>>> Kunpeng DMA engine. Also usual assorted updates to drivers.
>>>
>>> The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
>>>
>>> Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
>>>
>>> are available in the Git repository at:
>>>
>>> git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-5.6-rc1
>>>
>>> for you to fetch changes up to 71723a96b8b1367fefc18f60025dae792477d602:
>>>
>>> dmaengine: Create symlinks between DMA channels and slaves (2020-01-24 11:41:32 +0530)
>>>
>>> ----------------------------------------------------------------
>>> dmaengine updates for v5.6-rc1
>> ...
>>>
>>> Peter Ujfalusi (9):
>>> dmaengine: doc: Add sections for per descriptor metadata support
>>
>> This broke the docs build for me with:
>>
>> Sphinx parallel build error:
>> docutils.utils.SystemMessage: /linux/Documentation/driver-api/dmaengine/client.rst:155: (SEVERE/4) Unexpected section title.
>
> Thanks for the report.
>
>> Optional: per descriptor metadata
>> ---------------------------------
>>
>>
>> The patch below fixes the build. It may not produce the output you
>> intended, it just makes it bold rather than a heading, but it doesn't
>> really make sense to have a heading inside a numbered list.
>>
>> diff --git a/Documentation/driver-api/dmaengine/client.rst b/Documentation/driver-api/dmaengine/client.rst
>> index a9a7a3c84c63..343df26e73e8 100644
>> --- a/Documentation/driver-api/dmaengine/client.rst
>> +++ b/Documentation/driver-api/dmaengine/client.rst
>> @@ -151,8 +151,8 @@ DMA usage
>> 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 modified this to below as this:
>
> --- 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
> +---------------------------------
> DMAengine provides two ways for metadata support.
>
> DESC_METADATA_CLIENT
>
> And I will add this as fixes and it should be in linux-next tomorrow
Sorry for breaking the build and thanks Vinod for the quick fix!
>
> Thanks
>
- Péter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2020-01-28 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200127145835.GI2841@vkoul-mobl>
2020-01-28 11:50 ` Docs build broken by driver-api/dmaengine/client.rst ? (was Re: [GIT PULL]: dmaengine updates for v5.6-rc1) Michael Ellerman
2020-01-28 12:24 ` Vinod Koul
2020-01-28 12:35 ` Peter Ujfalusi [this message]
2020-01-29 7:47 ` Matthew Wilcox
2020-01-29 5:29 ` Michael Ellerman
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=f88ed09c-6244-71e5-3be4-b733ee348b79@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).