From: Randy Dunlap <rdunlap@infradead.org>
To: Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Tero Kristo <kristo@kernel.org>
Cc: vigneshr@ti.com, praneeth@ti.com, u-kumar1@ti.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Peter Ujfalusi <peter.ujfalusi@gmail.com>
Subject: Re: [PATCH V2] soc: ti: k3-ringacc: Fixup documentation errors
Date: Tue, 20 Jun 2023 19:40:22 -0700 [thread overview]
Message-ID: <a1dca14c-7d1e-e252-e081-8b24b9971adf@infradead.org> (raw)
In-Reply-To: <20230621023442.275128-1-nm@ti.com>
On 6/20/23 19:34, Nishanth Menon wrote:
> Fixup couple of misses in documentation. This squashes the following
> warnings:
> drivers/soc/ti/k3-ringacc.c:135: warning: Function parameter or member 'tdown_complete' not described in 'k3_ring_state'
> drivers/soc/ti/k3-ringacc.c:238: warning: expecting prototype for struct k3_ringacc. Prototype was for struct k3_ringacc_soc_data instead
>
> While at this, replace "w/a" to indicate workaround to help clarify.
>
> Cc: Peter Ujfalusi <peter.ujfalusi@gmail.com>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> Changes since V1:
> * Fixedup a couple of places where "w/a" is used - replaced with
> "workaround" to indicate quirk workaround
Thanks for that. Good change.
> * Picked up Randy's Reviewed-by.
>
> V1: https://lore.kernel.org/all/20230621022407.270842-1-nm@ti.com/
>
> drivers/soc/ti/k3-ringacc.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/soc/ti/k3-ringacc.c b/drivers/soc/ti/k3-ringacc.c
> index 8f131368a758..999403e1b9e0 100644
> --- a/drivers/soc/ti/k3-ringacc.c
> +++ b/drivers/soc/ti/k3-ringacc.c
> @@ -125,6 +125,7 @@ struct k3_ring_ops {
> * @occ: Occupancy
> * @windex: Write index
> * @rindex: Read index
> + * @tdown_complete: Tear down complete state
> */
> struct k3_ring_state {
> u32 free;
> @@ -192,7 +193,7 @@ struct k3_ringacc_ops {
> * @num_rings: number of ring in RA
> * @rings_inuse: bitfield for ring usage tracking
> * @rm_gp_range: general purpose rings range from tisci
> - * @dma_ring_reset_quirk: DMA reset w/a enable
> + * @dma_ring_reset_quirk: DMA reset workaround enable
> * @num_proxies: number of RA proxies
> * @proxy_inuse: bitfield for proxy usage tracking
> * @rings: array of rings descriptors (struct @k3_ring)
> @@ -229,9 +230,9 @@ struct k3_ringacc {
> };
>
> /**
> - * struct k3_ringacc - Rings accelerator SoC data
> + * struct k3_ringacc_soc_data - Rings accelerator SoC data
> *
> - * @dma_ring_reset_quirk: DMA reset w/a enable
> + * @dma_ring_reset_quirk: DMA reset workaround enable
> */
> struct k3_ringacc_soc_data {
> unsigned dma_ring_reset_quirk:1;
--
~Randy
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-21 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 2:34 [PATCH V2] soc: ti: k3-ringacc: Fixup documentation errors Nishanth Menon
2023-06-21 2:40 ` Randy Dunlap [this message]
2023-07-12 14:31 ` Nishanth Menon
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=a1dca14c-7d1e-e252-e081-8b24b9971adf@infradead.org \
--to=rdunlap@infradead.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.ujfalusi@gmail.com \
--cc=praneeth@ti.com \
--cc=ssantosh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
/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