Archive-only list for patches
 help / color / mirror / Atom feed
From: <gregkh@linuxfoundation.org>
To: alexander@tsoy.me,gregkh@linuxfoundation.org,jeff.johnson@oss.qualcomm.com,patches@lists.linux.dev,quic_ppranees@quicinc.com,sashal@kernel.org
Cc: <stable-commits@vger.kernel.org>
Subject: Patch "Revert "wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process"" has been added to the 6.14-stable tree
Date: Tue, 22 Apr 2025 15:07:22 +0200	[thread overview]
Message-ID: <2025042222-charter-battery-fefd@gregkh> (raw)
In-Reply-To: <20250422120237.228960-1-alexander@tsoy.me>


This is a note to let you know that I've just added the patch titled

    Revert "wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process"

to the 6.14-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     revert-wifi-ath12k-fix-invalid-entry-fetch-in-ath12k_dp_mon_srng_process.patch
and it can be found in the queue-6.14 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


From alexander@tsoy.me  Tue Apr 22 15:03:50 2025
From: Alexander Tsoy <alexander@tsoy.me>
Date: Tue, 22 Apr 2025 15:02:36 +0300
Subject: Revert "wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process"
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: patches@lists.linux.dev, P Praneesh <quic_ppranees@quicinc.com>, Jeff Johnson <jeff.johnson@oss.qualcomm.com>, Sasha Levin <sashal@kernel.org>
Message-ID: <20250422120237.228960-1-alexander@tsoy.me>

From: Alexander Tsoy <alexander@tsoy.me>

This reverts commit 0c1015493f0e3979bcbd3a12ebc0977578c87f21 which is
commit 63fdc4509bcf483e79548de6bc08bf3c8e504bb3 upstream as it was
backported incorrectly.

A subsequent commit will re-backport the original patch.

Signed-off-by: Alexander Tsoy <alexander@tsoy.me>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 drivers/net/wireless/ath/ath12k/dp_mon.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/net/wireless/ath/ath12k/dp_mon.c
+++ b/drivers/net/wireless/ath/ath12k/dp_mon.c
@@ -2473,7 +2473,7 @@ int ath12k_dp_mon_rx_process_stats(struc
 		dest_idx = 0;
 move_next:
 		ath12k_dp_mon_buf_replenish(ab, buf_ring, 1);
-		ath12k_hal_srng_dst_get_next_entry(ab, srng);
+		ath12k_hal_srng_src_get_next_entry(ab, srng);
 		num_buffs_reaped++;
 	}
 


Patches currently in stable-queue which might be from alexander@tsoy.me are

queue-6.14/revert-wifi-ath12k-fix-invalid-entry-fetch-in-ath12k_dp_mon_srng_process.patch

      parent reply	other threads:[~2025-04-22 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 12:02 [PATCH 6.14.y v2 1/2] Revert "wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process" Alexander Tsoy
2025-04-22 12:02 ` [PATCH 6.14.y v2 2/2] wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process Alexander Tsoy
2025-04-22 13:06   ` Greg Kroah-Hartman
2025-04-22 13:07 ` gregkh [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=2025042222-charter-battery-fefd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander@tsoy.me \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=patches@lists.linux.dev \
    --cc=quic_ppranees@quicinc.com \
    --cc=sashal@kernel.org \
    --cc=stable-commits@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