From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: linux-doc@vger.kernel.org, linux-rdma@vger.kernel.org,
intel-gfx@lists.freedesktop.org,
"Jonathan Corbet" <corbet@lwn.net>,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
linaro-mm-sig@lists.linaro.org, dri-devel@lists.freedesktop.org,
"Sumit Semwal" <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] dma-buf.rst: repair length of title underline
Date: Mon, 10 Aug 2020 13:25:40 +0200 [thread overview]
Message-ID: <7d434810-79bd-89a3-18f8-c5c2a2524822@gmail.com> (raw)
In-Reply-To: <20200809061739.16803-1-lukas.bulwahn@gmail.com>
Am 09.08.20 um 08:17 schrieb Lukas Bulwahn:
> With commit 72b6ede73623 ("dma-buf.rst: Document why indefinite fences are
> a bad idea"), document generation warns:
>
> Documentation/driver-api/dma-buf.rst:182: \
> WARNING: Title underline too short.
>
> Repair length of title underline to remove warning.
>
> Fixes: 72b6ede73623 ("dma-buf.rst: Document why indefinite fences are a bad idea")
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Acked-by: Christian König <christian.koenig@amd.com>
Should I pick it up into drm-misc-next?
> ---
> Daniel, please pick this minor non-urgent fix to your new documentation.
>
> Documentation/driver-api/dma-buf.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/driver-api/dma-buf.rst b/Documentation/driver-api/dma-buf.rst
> index 100bfd227265..13ea0cc0a3fa 100644
> --- a/Documentation/driver-api/dma-buf.rst
> +++ b/Documentation/driver-api/dma-buf.rst
> @@ -179,7 +179,7 @@ DMA Fence uABI/Sync File
> :internal:
>
> Indefinite DMA Fences
> -~~~~~~~~~~~~~~~~~~~~
> +~~~~~~~~~~~~~~~~~~~~~
>
> At various times &dma_fence with an indefinite time until dma_fence_wait()
> finishes have been proposed. Examples include:
next prev parent reply other threads:[~2020-08-10 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 6:17 [PATCH] dma-buf.rst: repair length of title underline Lukas Bulwahn
2020-08-10 11:25 ` Christian König [this message]
2020-08-10 13:06 ` Daniel Vetter
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=7d434810-79bd-89a3-18f8-c5c2a2524822@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=sumit.semwal@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