public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Hari Prasath <gehariprasath@ti.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>, <nm@ti.com>,
	<ssantosh@kernel.org>
Cc: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>
Subject: Re: [PATCH v2] soc: ti: k3-ringacc: Fix access mode for k3_ringacc_ring_pop_tail_io/proxy
Date: Tue, 5 May 2026 19:04:35 +0530	[thread overview]
Message-ID: <1a379b9a-cd2d-43b6-ab90-c605fff432e9@ti.com> (raw)
In-Reply-To: <20260501124129.362192-1-s-vadapalli@ti.com>

On 01/05/26 6:10 pm, Siddharth Vadapalli wrote:
> k3_ringacc_ring_pop_tail_io() and k3_ringacc_ring_pop_tail_proxy()
> incorrectly use K3_RINGACC_ACCESS_MODE_POP_HEAD instead of
> K3_RINGACC_ACCESS_MODE_POP_TAIL. This will result in ring elements being
> popped in the reverse order of that which the caller expects. Fix this.
> 
> Fixes: 3277e8aa2504 ("soc: ti: k3: add navss ringacc driver")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>

Thanks Siddharth.LGTM.

Reviewed-by: Hari Prasath Gujulan Elango <gehariprasath@ti.com>

> ---
> 
> Patch is based on commit
> 26fd6bff2c05 Merge tag 'mtd/fixes-for-7.1-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux
> of Mainline Linux.
> 
> v1:
> https://lore.kernel.org/r/20260413065125.627180-1-s-vadapalli@ti.com/
> Changes since v1:
> - Updated commit message and fixed k3_ringacc_ring_pop_tail_proxy() as
>    well based on feedback from Hari Prasath G E <gehariprasath@ti.com>
>    at:
>    https://lore.kernel.org/r/d36239c2-98d5-4e5b-b99e-470f4d753a52@ti.com/
> 
>   drivers/soc/ti/k3-ringacc.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/soc/ti/k3-ringacc.c b/drivers/soc/ti/k3-ringacc.c
> index 7602b8a909b0..e2ca380812d2 100644
> --- a/drivers/soc/ti/k3-ringacc.c
> +++ b/drivers/soc/ti/k3-ringacc.c
> @@ -1012,7 +1012,7 @@ static int k3_ringacc_ring_pop_head_proxy(struct k3_ring *ring, void *elem)
>   static int k3_ringacc_ring_pop_tail_proxy(struct k3_ring *ring, void *elem)
>   {
>   	return k3_ringacc_ring_access_proxy(ring, elem,
> -					    K3_RINGACC_ACCESS_MODE_POP_HEAD);
> +					    K3_RINGACC_ACCESS_MODE_POP_TAIL);
>   }
>   
>   static int k3_ringacc_ring_access_io(struct k3_ring *ring, void *elem,
> @@ -1083,7 +1083,7 @@ static int k3_ringacc_ring_pop_io(struct k3_ring *ring, void *elem)
>   static int k3_ringacc_ring_pop_tail_io(struct k3_ring *ring, void *elem)
>   {
>   	return k3_ringacc_ring_access_io(ring, elem,
> -					 K3_RINGACC_ACCESS_MODE_POP_HEAD);
> +					 K3_RINGACC_ACCESS_MODE_POP_TAIL);
>   }
>   
>   /*



      reply	other threads:[~2026-05-05 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 12:40 [PATCH v2] soc: ti: k3-ringacc: Fix access mode for k3_ringacc_ring_pop_tail_io/proxy Siddharth Vadapalli
2026-05-05 13:34 ` Hari Prasath [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=1a379b9a-cd2d-43b6-ab90-c605fff432e9@ti.com \
    --to=gehariprasath@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=s-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=ssantosh@kernel.org \
    --cc=stable@vger.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