From: Yang Li <yang.lee@linux.alibaba.com>
To: ysato@users.sourceforge.jp, dalias@libc.org,
glaubitz@physik.fu-berlin.de
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Yang Li <yang.lee@linux.alibaba.com>
Subject: [PATCH -next] dma: Add dev_id parameter description in request_dma_bycap
Date: Fri, 19 Apr 2024 17:02:59 +0800 [thread overview]
Message-ID: <20240419090259.39542-1-yang.lee@linux.alibaba.com> (raw)
This patch adds the missing description for the dev_id parameter in the
kernel documentation for the request_dma_bycap function.
Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
---
arch/sh/drivers/dma/dma-api.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/sh/drivers/dma/dma-api.c b/arch/sh/drivers/dma/dma-api.c
index 89cd4a3b4cca..65005d348877 100644
--- a/arch/sh/drivers/dma/dma-api.c
+++ b/arch/sh/drivers/dma/dma-api.c
@@ -116,6 +116,7 @@ static int search_cap(const char **haystack, const char *needle)
* request_dma_bycap - Allocate a DMA channel based on its capabilities
* @dmac: List of DMA controllers to search
* @caps: List of capabilities
+ * @dev_id: Unique identifier for the device that is requesting a DMA channel
*
* Search all channels of all DMA controllers to find a channel which
* matches the requested capabilities. The result is the channel
--
2.20.1.7.g153144c
next reply other threads:[~2024-04-19 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:02 Yang Li [this message]
2024-04-19 9:13 ` [PATCH -next] dma: Add dev_id parameter description in request_dma_bycap Geert Uytterhoeven
2024-04-19 9:21 ` John Paul Adrian Glaubitz
2024-05-02 10:31 ` John Paul Adrian Glaubitz
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=20240419090259.39542-1-yang.lee@linux.alibaba.com \
--to=yang.lee@linux.alibaba.com \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).