From: sashiko-bot@kernel.org
To: "Pavel Begunkov" <asml.silence@gmail.com>
Cc: dri-devel@lists.freedesktop.org, media-ci@linuxtv.org
Subject: Re: [PATCH v2 2/2] dma-buf-io: document dma_buf_io_init_map
Date: Fri, 16 Oct 2026 10:09:54 +0000 [thread overview]
Message-ID: <sashiko-outbox-174125@kernel.org> (raw)
In-Reply-To: <a9fdfbe6e447ac583f4d3a3f981b203141a624c4.1792144609.git.asml.silence@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dma-buf: incorrect documentation of map parameter direction
--
commit 1158f35d78a501cf423bc44ae35a1645c81c621d
Author: Pavel Begunkov <asml.silence@gmail.com>
dma-buf-io: document dma_buf_io_init_map
This commit adds a kerneldoc for dma_buf_io_init_map().
> diff --git a/drivers/dma-buf/dma-buf-io.c b/drivers/dma-buf/dma-buf-io.c
> index e432194a5dfc0..8440151de8600 100644
> --- a/drivers/dma-buf/dma-buf-io.c
> +++ b/drivers/dma-buf/dma-buf-io.c
> @@ -43,6 +43,18 @@ static void dma_buf_io_kill_map(struct dma_buf_io_ctx *ctx)
> dma_buf_io_map_release(map);
> }
>
> +/**
> + * dma_buf_io_init_map - Initialise the map.
> + * @ctx: [in] dma-buf I/O context the map is created for
> + * @map: [in] dma-buf I/O map
[Severity: Low]
Is the [in] annotation correct for the map parameter here? Since
dma_buf_io_init_map() initializes the internal fields of the map struct,
this functions as an output parameter. Should this be documented as [out]
or [in,out] instead?
> + * @sgt: [in] the backing scatter-gather table
> + *
> + * Importer's helper that initialises @map for the provided I/O context
> + * and scatter-gather table. The importer should call it once for each map
> + * on creation.
> + *
> + * Return: 0 on success, or a negative errno code otherwise.
> + */
> int dma_buf_io_init_map(struct dma_buf_io_ctx *ctx, struct dma_buf_io_map *map,
> struct sg_table *sgt)
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1792144609.git.asml.silence@gmail.com?part=2
next prev parent reply other threads:[~2026-10-16 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:58 [PATCH v2 0/2] clean up dma-buf-io kerneldocs Pavel Begunkov
2026-10-16 9:58 ` [PATCH v2 1/2] dma-buf-io: fix typos in kernel docs Pavel Begunkov
2026-10-16 9:58 ` [PATCH v2 2/2] dma-buf-io: document dma_buf_io_init_map Pavel Begunkov
2026-10-16 10:09 ` sashiko-bot [this message]
2026-10-16 14:28 ` [PATCH v2 0/2] clean up dma-buf-io kerneldocs Jens Axboe
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=sashiko-outbox-174125@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=asml.silence@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=media-ci@linuxtv.org \
--cc=sashiko-reviews@lists.linux.dev \
/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