From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Yang Li <yang.lee@linux.alibaba.com>,
ysato@users.sourceforge.jp, dalias@libc.org
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] dma: Add dev_id parameter description in request_dma_bycap
Date: Thu, 02 May 2024 12:31:54 +0200 [thread overview]
Message-ID: <98810f30345bff398b23f61ffcf5ecb874402c0a.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20240419090259.39542-1-yang.lee@linux.alibaba.com>
Hi Yang,
On Fri, 2024-04-19 at 17:02 +0800, Yang Li wrote:
> 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
This patch is now obsolete since search_cap() was removed in for-next by Geert
Uytterhoven in 89256d73 ("sh: dma: Remove unused functionality").
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2024-05-02 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:02 [PATCH -next] dma: Add dev_id parameter description in request_dma_bycap Yang Li
2024-04-19 9:13 ` Geert Uytterhoeven
2024-04-19 9:21 ` John Paul Adrian Glaubitz
2024-05-02 10:31 ` John Paul Adrian Glaubitz [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=98810f30345bff398b23f61ffcf5ecb874402c0a.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=yang.lee@linux.alibaba.com \
--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).