From: Bagas Sanjaya <bagasdotme@gmail.com>
To: mhklinux@outlook.com, robin.murphy@arm.com, joro@8bytes.org,
will@kernel.org, hch@lst.de, m.szyprowski@samsung.com,
corbet@lwn.net, iommu@lists.linux.dev,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
petr@tesarici.cz, roberto.sassu@huaweicloud.com
Cc: Mao Zhu <zhumao001@208suo.com>, Ran Sun <sunran001@208suo.com>,
Xiang wangx <wangxiang@cdjrlc.com>,
Shaomin Deng <dengshaomin@cdjrlc.com>,
Charles Han <hanchunchao@inspur.com>,
Attreyee M <tintinm2017@gmail.com>, Josh Don <joshdon@google.com>,
YouHong Li <liyouhong@kylinos.cn>
Subject: Re: [PATCH v2 1/1] Documentation/core-api: Add swiotlb documentation
Date: Thu, 25 Apr 2024 16:13:32 +0700 [thread overview]
Message-ID: <ZioevHI3wok_yiSv@archie.me> (raw)
In-Reply-To: <20240424150253.560999-1-mhklinux@outlook.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Wed, Apr 24, 2024 at 08:02:53AM -0700, mhkelley58@gmail.com wrote:
> From: Michael Kelley <mhklinux@outlook.com>
>
> There's currently no documentation for the swiotlb. Add documentation
> describing usage scenarios, the key APIs, and implementation details.
> Group the new documentation with other DMA-related documentation.
>
> Signed-off-by: Michael Kelley <mhklinux@outlook.com>
The doc LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-04-25 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 15:02 [PATCH v2 1/1] Documentation/core-api: Add swiotlb documentation mhkelley58
2024-04-25 9:13 ` Bagas Sanjaya [this message]
2024-04-26 6:18 ` Christoph Hellwig
2024-04-26 12:56 ` Jonathan Corbet
2024-04-26 16:29 ` Michael Kelley
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=ZioevHI3wok_yiSv@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dengshaomin@cdjrlc.com \
--cc=hanchunchao@inspur.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=joshdon@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liyouhong@kylinos.cn \
--cc=m.szyprowski@samsung.com \
--cc=mhklinux@outlook.com \
--cc=petr@tesarici.cz \
--cc=roberto.sassu@huaweicloud.com \
--cc=robin.murphy@arm.com \
--cc=sunran001@208suo.com \
--cc=tintinm2017@gmail.com \
--cc=wangxiang@cdjrlc.com \
--cc=will@kernel.org \
--cc=zhumao001@208suo.com \
/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