From: Michael Ellerman <mpe@ellerman.id.au>
To: Vinod Koul <vkoul@kernel.org>
Cc: peter.ujfalusi@ti.com, 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: Wed, 29 Jan 2020 16:29:33 +1100 [thread overview]
Message-ID: <875zguhltu.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200128122415.GU2841@vkoul-mobl>
Vinod Koul <vkoul@kernel.org> writes:
> On 28-01-20, 22:50, Michael Ellerman wrote:
...
>
> 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
Thanks!
cheers
prev parent reply other threads:[~2020-01-29 5:29 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
2020-01-29 7:47 ` Matthew Wilcox
2020-01-29 5:29 ` Michael Ellerman [this message]
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=875zguhltu.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--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).