From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Accelerators <linux-accelerators@lists.ozlabs.org>
Cc: Zhangfei Gao <zhangfei.gao@linaro.org>,
Zhou Wang <wangzhou1@hisilicon.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: uacce: Add explicit title
Date: Sun, 2 Nov 2025 20:58:32 -0800 [thread overview]
Message-ID: <e95704fd-68fa-4093-835c-ca220a9c3f5d@infradead.org> (raw)
In-Reply-To: <20251103025950.23159-1-bagasdotme@gmail.com>
On 11/2/25 6:59 PM, Bagas Sanjaya wrote:
> Uacce docs' sections are listed in misc-devices toctree instead due to
> lack of explicit docs title. Add it to clean up the toctree.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/misc-devices/uacce.rst | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/misc-devices/uacce.rst b/Documentation/misc-devices/uacce.rst
> index 1db412e9b1a380..2ca539b7d6c799 100644
> --- a/Documentation/misc-devices/uacce.rst
> +++ b/Documentation/misc-devices/uacce.rst
> @@ -1,7 +1,10 @@
> .. SPDX-License-Identifier: GPL-2.0
>
> -Introduction of Uacce
> ----------------------
> +Uacce (Unified/User-space-acess-intended Accelerator Framework)
access ?
> +===============================================================
> +
> +Introduction
> +------------
>
> Uacce (Unified/User-space-access-intended Accelerator Framework) targets to
> provide Shared Virtual Addressing (SVA) between accelerators and processes.
>
> base-commit: e5e7ca66a7fc6b8073c30a048e1157b88d427980
--
~Randy
next prev parent reply other threads:[~2025-11-03 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 2:59 Bagas Sanjaya
2025-11-03 4:58 ` Randy Dunlap [this message]
2025-11-03 5:15 ` Randy Dunlap
2025-11-03 9:19 ` Bagas Sanjaya
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=e95704fd-68fa-4093-835c-ca220a9c3f5d@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-accelerators@lists.ozlabs.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=zhangfei.gao@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
all inboxes | Powered by JetHome®