All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: linux-trace-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	imx@lists.linux.dev, vkoul@kernel.org,
	linux-sunxi@lists.linux.dev, Frank.Li@kernel.org
Subject: Re: [PATCH v4 4/4] dmaengine: add union chan_dev for dma_chan::dev for clarity
Date: Wed, 09 Sep 2026 16:32:10 +0000	[thread overview]
Message-ID: <20260909163210.DFF521F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260909-dma-chan_dev-rename-v4-4-d8fb6892a70f@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Kernel-doc build warning introduced by removing the `@dev:` documentation tag while retaining `dev` in the structure.
--

commit 0443f99a737aae399ea7d93dad586cf7543a34af
Author: Frank Li <Frank.Li@nxp.com>

dmaengine: add union chan_dev for dma_chan::dev for clarity

This commit introduces an anonymous union in struct dma_chan to provide 
a chan_dev member alongside the existing dev member, clarifying its purpose as 
the per-channel device. It also updates the kernel-doc to document chan_dev 
instead of dev.

> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> index 33aa1bfc8fb84..c3a49a33307c6 100644
> --- a/include/linux/dmaengine.h
> +++ b/include/linux/dmaengine.h
> @@ -325,7 +325,8 @@ struct dma_router {
>   * @lock: protect between config and prepare transfer when driver have not
>   *	  implemented callback device_prep_config_sg().
>   * @chan_id: channel ID for sysfs
> - * @dev: class device for sysfs
> + * @chan_dev: class channel device for sysfs, some device use it for per-channel
> + *            IOMMU mapping.
>   * @name: backlink name for sysfs
>   * @dbg_client_name: slave name for debugfs in format:

[ ... ]

> @@ -351,7 +352,14 @@ struct dma_chan {
>  
>  	/* sysfs */
>  	int chan_id;
> -	struct dma_chan_dev *dev;
> +	union {
> +		struct dma_chan_dev *chan_dev;
> +		/*
> +		 * Use chan_dev; dev will be removed once all users are
> +		 * converted.
> +		 */
> +		struct dma_chan_dev *dev;
> +	};

[Severity: Low]
Does this removal of the @dev kernel-doc tag trigger a kernel-doc build 
warning?

Since the dev member is kept inside an anonymous union for backward 
compatibility, and the kernel-doc parser flattens anonymous unions, it 
typically expects all non-private members to be explicitly documented. 

Would it be better to retain the @dev documentation tag with a note 
indicating it is deprecated, or mark it as private to avoid the build 
warning?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260909-dma-chan_dev-rename-v4-0-d8fb6892a70f@nxp.com?part=4

      reply	other threads:[~2026-09-09 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 16:22 [PATCH v4 0/4] dmaengine: rename dma_chan::dev to dma_chan::chan_dev for clarity Frank.Li
2026-09-09 16:22 ` [PATCH v4 1/4] dmaengine: vchan: add vchan_chan_name() to get channel device name Frank.Li
2026-09-09 16:36   ` sashiko-bot
2026-09-09 16:22 ` [PATCH v4 2/4] dmaengine: use dma_chan_name() helper to get per-channel " Frank.Li
2026-09-09 16:22 ` [PATCH v4 3/4] dmaengine: add (dmaengine|vchan)_chan_dev() helper Frank.Li
2026-09-09 16:22 ` [PATCH v4 4/4] dmaengine: add union chan_dev for dma_chan::dev for clarity Frank.Li
2026-09-09 16:32   ` sashiko-bot [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=20260909163210.DFF521F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@oss.nxp.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.