From: anish kumar <yesanishhere@gmail.com>
To: corbet@lwn.net, tj@kernel.org, akpm@linux-foundation.org,
ptesarik@suse.com, xavier_qy@163.com, vbabka@suse.cz,
tintinm2017@gmail.com
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
anish kumar <yesanishhere@gmail.com>
Subject: [RFC PATCH 0/2] modernize DMA api documentation
Date: Tue, 12 Nov 2024 22:34:23 -0800 [thread overview]
Message-ID: <20241113063425.21042-1-yesanishhere@gmail.com> (raw)
Dear maintainers,
This patch series is inspired by the ongoing discussion in the following thread:
https://lore.kernel.org/lkml/20241111063847.GB23992@lst.de/
As part of an effort to modernize the documentation, the first patch in
this series converts the relevant document to use kernel-doc comments directly
within the source code, replacing the previous method of manually adding
documentation. This change will help streamline the documentation workflow and
ensure it remains synchronized with the code.
I am still getting below errors and wondering if there is a better
way to write this patch.
/home/ANT.AMAZON.COM/anishkmr/Downloads/linux/Documentation/core-api/dma-api:89:
./mm/dmapool.c:229: WARNING: Duplicate C declaration, also defined at
core-api/mm-api:224. Declaration is:
'.. c:function:: struct dma_pool *dma_pool_create (const char *name,
struct device *dev, size_t size, size_t align, size_t boundary)'.
/home/ANT.AMAZON.COM/anishkmr/Downloads/linux/Documentation/core-api/dma-api:92:
./mm/dmapool.c:420: WARNING: Duplicate C declaration, also defined at
core-api/mm-api:404. Declaration is:
'.. c:function:: void *dma_pool_alloc (struct dma_pool *pool, gfp_t mem_flags,
dma_addr_t *handle)'.
/home/ANT.AMAZON.COM/anishkmr/Downloads/linux/Documentation/core-api/dma-api:98:
./mm/dmapool.c:229: WARNING: Duplicate C declaration, also defined at
core-api/mm-api:224. Declaration is:
'.. c:function:: struct dma_pool *dma_pool_create (const char *name,
struct device *dev, size_t size, size_t align, size_t boundary)'.
/home/ANT.AMAZON.COM/anishkmr/Downloads/linux/Documentation/core-api/dma-api:101:
./mm/dmapool.c:466: WARNING: Duplicate C declaration, also defined at
core-api/mm-api:450. Declaration is:
'.. c:function:: void dma_pool_free (struct dma_pool *pool, void *vaddr,
dma_addr_t dma)'.
/home/ANT.AMAZON.COM/anishkmr/Downloads/linux/Documentation/core-api/dma-api:104:
./mm/dmapool.c:366: WARNING: Duplicate C declaration, also defined at
core-api/mm-api:360.
Thank you for considering this patch. I look forward to your feedback.
anish kumar (2):
dmapool: Improve dma api kernel-doc comments
dmapool: Documentation: use the kernel-doc comment
Documentation/core-api/dma-api.rst | 66 ++++++------------------------
mm/dmapool.c | 40 ++++++++++++------
2 files changed, 40 insertions(+), 66 deletions(-)
--
2.39.5 (Apple Git-154)
next reply other threads:[~2024-11-13 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 6:34 anish kumar [this message]
2024-11-13 6:34 ` [RFC PATCH 1/2] dmapool: Improve dma api kernel-doc comments anish kumar
2024-11-13 6:34 ` [RFC PATCH 2/2] dmapool: Documentation: use the kernel-doc comment anish kumar
2024-11-14 6:12 ` [RFC PATCH 0/2] modernize DMA api documentation Randy Dunlap
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=20241113063425.21042-1-yesanishhere@gmail.com \
--to=yesanishhere@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ptesarik@suse.com \
--cc=tintinm2017@gmail.com \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
--cc=xavier_qy@163.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