DMA Engine development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: vkoul@kernel.org, Frank.Li@kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH] dma: bestcomm: gen_bd: split struct bcom_psc_params from array definition
Date: Thu, 28 May 2026 20:43:14 +0000	[thread overview]
Message-ID: <20260528204314.881241F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260528203534.137794-1-rosenp@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The commit completely removes the documentation block for `bcom_psc_params` instead of fixing its kernel-doc format or retaining it.
--

commit ca2ec5c8d7bd735d412b27e8045b30e921157753
Author: Rosen Penev <rosenp@gmail.com>

dma: bestcomm: gen_bd: split struct bcom_psc_params from array definition

This commit separates the struct bcom_psc_params definition from its
array declaration. The split is intended to fix kernel-doc parser
confusion caused by the combined struct-definition-with-initializer
pattern.

> diff --git a/drivers/dma/bestcomm/gen_bd.c b/drivers/dma/bestcomm/gen_bd.c
> index 8a24a5cbc2633..0b400a76adcf0 100644
> --- a/drivers/dma/bestcomm/gen_bd.c
> +++ b/drivers/dma/bestcomm/gen_bd.c
> @@ -253,18 +253,14 @@ EXPORT_SYMBOL_GPL(bcom_gen_bd_tx_release);
>   * PSC support code
>   */
>  
> -/**
> - * bcom_psc_parameters - Bestcomm initialization value table for PSC devices
> - *
> - * This structure is only used internally.  It is a lookup table for PSC
> - * specific parameters to bestcomm tasks.
> - */
> -static struct bcom_psc_params {

[Severity: Low]
This isn't a bug, but the commit message mentions fixing the kernel-doc
parser confusion by splitting the struct and array definition, yet the
actual kernel-doc block is completely removed here.

Was it intentional to drop this documentation entirely rather than keeping
it attached to the separated structure or array?

> +struct bcom_psc_params {
>  	int rx_initiator;
>  	int rx_ipr;

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260528203534.137794-1-rosenp@gmail.com?part=1

      reply	other threads:[~2026-05-28 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 20:35 [PATCH] dma: bestcomm: gen_bd: split struct bcom_psc_params from array definition Rosen Penev
2026-05-28 20:43 ` 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=20260528204314.881241F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=rosenp@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox