Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Pardeep Kaur <pardeep.kaur@oss.qualcomm.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
	Hariharan Ramanathan <hariharan.ramanathan@oss.qualcomm.com>
Subject: Re: [PATCH ath-next v4 4/8] wifi: ath12k: add device DP stats reset support via debugfs
Date: Thu, 24 Sep 2026 08:30:54 -0700	[thread overview]
Message-ID: <8e027ef0-6956-4766-9ba1-55963bb6c537@oss.qualcomm.com> (raw)
In-Reply-To: <30303e94-f0a3-4e91-8690-006fea92dff4@oss.qualcomm.com>

On 9/24/2026 12:55 AM, Pardeep Kaur wrote:
> On 23-09-2026 05:42, Jeff Johnson wrote:
>> On 8/18/2026 10:32 PM, Pardeep Kaur wrote:
>>> From: Hariharan Ramanathan <hariharan.ramanathan@oss.qualcomm.com>
>>> Add a write handler to the device_dp_stats debugfs file so that
>>> writing 'reset' clears all device DP stats counters. Change the file
>>> mode from 0400 to 0600 to allow write access. Use
>>> simple_write_to_buffer() to correctly handle partial writes and
>>> non-zero ppos, consistent with ath12k_write_simulate_fw_crash() in
>> in what? the last sentence seems to be truncated. Or perhaps just s/ in$/./?
>> if there are no other comments in the thread there is no need to repost just
>> for this. Instead just let me know what text you really want here.
> debugfs.c.

since this patch is already modifying debugfs.c, I did s/ in/./ in my pending
branch:

non-zero ppos, consistent with ath12k_write_simulate_fw_crash().

https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/commit/?h=pending&id=3bd2457570ab0a4ca5e7e354e7b6d8703ece6c93


  reply	other threads:[~2026-09-24 15:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19  5:32 [PATCH ath-next v4 0/8] wifi: ath12k: extend device DP stats for TX and RX observability Pardeep Kaur
2026-08-19  5:32 ` [PATCH ath-next v4 1/8] wifi: ath12k: fix out-of-bounds access on TX stats arrays Pardeep Kaur
2026-08-19  5:32 ` [PATCH ath-next v4 2/8] wifi: ath12k: rename wbm_status to htt_status in HTT TX completion Pardeep Kaur
2026-08-19  5:32 ` [PATCH ath-next v4 3/8] wifi: ath12k: add TCL ring TX buffer allocation failure counter Pardeep Kaur
2026-08-19  5:32 ` [PATCH ath-next v4 4/8] wifi: ath12k: add device DP stats reset support via debugfs Pardeep Kaur
2026-09-23  0:12   ` Jeff Johnson
2026-09-24  7:55     ` Pardeep Kaur
2026-09-24 15:30       ` Jeff Johnson [this message]
2026-08-19  5:32 ` [PATCH ath-next v4 5/8] wifi: ath12k: add WBM RX error drop statistics Pardeep Kaur
2026-08-19  5:32 ` [PATCH ath-next v4 6/8] wifi: ath12k: track per-ring RX sent-to-stack count Pardeep Kaur
2026-08-19  5:32 ` [PATCH ath-next v4 7/8] wifi: ath12k: fix 1-based ring index in REO Rx Received debugfs output Pardeep Kaur
2026-08-19  5:32 ` [PATCH ath-next v4 8/8] wifi: ath12k: add WBM SW desc fallback counter Pardeep Kaur
2026-09-23  8:47 ` [PATCH ath-next v4 0/8] wifi: ath12k: extend device DP stats for TX and RX observability Baochen Qiang
2026-09-23 12:49 ` Rameshkumar Sundaram
2026-09-25 15:26 ` Jeff Johnson

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=8e027ef0-6956-4766-9ba1-55963bb6c537@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=ath12k@lists.infradead.org \
    --cc=hariharan.ramanathan@oss.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pardeep.kaur@oss.qualcomm.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