From: "Kumar, Udit" <u-kumar1@ti.com>
To: Karl Mehltretter <kmehltretter@gmail.com>,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>
Subject: Re: [PATCH v2 2/2] soc: ti: k3-ringacc: Fix DMA ring initialization kernel-doc
Date: Wed, 23 Sep 2026 18:33:15 +0530 [thread overview]
Message-ID: <40b6706d-fa68-43d3-8abd-bd8b70e4cb89@ti.com> (raw)
In-Reply-To: <20260923061658.20140-2-kmehltretter@gmail.com>
On 9/23/2026 11:46 AM, Karl Mehltretter wrote:
> The heading for k3_ringacc_init_data repeats struct, so kernel-doc
> cannot match it to the declaration. Its three fields are also missing
> descriptions.
>
> Use the structure name and describe the firmware handle, device ID,
> and total number of available rings used during DMA ring initialization.
>
> Fixes: d782298c6f6b ("soc: ti: k3-ringacc: add AM64 DMA rings support.")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> ---
>
> Notes (ti-ringacc-v2):
> Changes in v2:
> - Describe num_rings as the total number of available rings in the
> comment and commit message, as pointed out by Udit Kumar.
>
> Patch 1 is unchanged.
>
> v1: https://lore.kernel.org/r/20260919163721.89044-1-kmehltretter@gmail.com/
>
> include/linux/soc/ti/k3-ringacc.h | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/soc/ti/k3-ringacc.h b/include/linux/soc/ti/k3-ringacc.h
> index 2de6031b9424..7b7fc237c08f 100644
> --- a/include/linux/soc/ti/k3-ringacc.h
> +++ b/include/linux/soc/ti/k3-ringacc.h
> @@ -254,7 +254,10 @@ u32 k3_ringacc_get_tisci_dev_id(struct k3_ring *ring);
> struct ti_sci_handle;
>
> /**
> - * struct struct k3_ringacc_init_data - Initialization data for DMA rings
> + * struct k3_ringacc_init_data - Initialization data for DMA rings
> + * @tisci: TI SCI firmware handle
> + * @tisci_dev_id: TI SCI device ID of the DMA controller
> + * @num_rings: Total number of available rings
> */
Reviewed-by: Udit Kumar <u-kumar1@ti.com>
> struct k3_ringacc_init_data {
> const struct ti_sci_handle *tisci;
prev parent reply other threads:[~2026-09-23 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 6:16 [PATCH v2 1/2] soc: ti: k3-ringacc: Correct ring API kernel-doc Karl Mehltretter
2026-09-23 6:16 ` [PATCH v2 2/2] soc: ti: k3-ringacc: Fix DMA ring initialization kernel-doc Karl Mehltretter
2026-09-23 13:03 ` Kumar, Udit [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=40b6706d-fa68-43d3-8abd-bd8b70e4cb89@ti.com \
--to=u-kumar1@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=kmehltretter@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=ssantosh@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
all inboxes | Powered by JetHome®