From: Michael Kelley <mhklinux@outlook.com>
To: Christoph Hellwig <hch@lst.de>, Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "robin.murphy@arm.com" <robin.murphy@arm.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"petr@tesarici.cz" <petr@tesarici.cz>,
"roberto.sassu@huaweicloud.com" <roberto.sassu@huaweicloud.com>
Subject: RE: [PATCH v4 1/1] Documentation/core-api: Add swiotlb documentation
Date: Thu, 2 May 2024 13:45:52 +0000 [thread overview]
Message-ID: <SN6PR02MB415704C5C2EF87C290D179C0D4182@SN6PR02MB4157.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20240502124927.GA20542@lst.de>
From: Christoph Hellwig <hch@lst.de> Sent: Thursday, May 2, 2024 5:49 AM
>
> Fixed.
Still has a typo -- "Reviewed-bu" instead of "Reviewed-by". :-)
Documentation/core-api: add swiotlb documentation
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>
Reviewed-bu: Bagas Sanjaya <bagasdotme@gmail.com>
Reviewed-by: Petr Tesarik <petr@tesarici.cz>
Signed-off-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2024-05-02 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 15:16 [PATCH v4 1/1] Documentation/core-api: Add swiotlb documentation mhkelley58
2024-05-01 16:27 ` Petr Tesařík
2024-05-02 0:46 ` Bagas Sanjaya
2024-05-02 5:52 ` Christoph Hellwig
2024-05-02 9:55 ` Bagas Sanjaya
2024-05-02 12:49 ` Christoph Hellwig
2024-05-02 13:45 ` Michael Kelley [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=SN6PR02MB415704C5C2EF87C290D179C0D4182@SN6PR02MB4157.namprd02.prod.outlook.com \
--to=mhklinux@outlook.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=petr@tesarici.cz \
--cc=roberto.sassu@huaweicloud.com \
--cc=robin.murphy@arm.com \
--cc=will@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 read-only IMAP folder(s) and NNTP newsgroup(s).