From: Kalle Valo <kvalo@kernel.org>
To: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
Venkateswara Naralasetty <quic_vnaralas@quicinc.com>
Subject: Re: [PATCH] wifi: ath11k: update proper pdev/vdev id for testmode command
Date: Wed, 26 Apr 2023 10:29:22 +0300 [thread overview]
Message-ID: <87a5yvt831.fsf@kernel.org> (raw)
In-Reply-To: <20230424092420.12794-1-quic_rajkbhag@quicinc.com> (Raj Kumar Bhagat's message of "Mon, 24 Apr 2023 14:54:20 +0530")
Raj Kumar Bhagat <quic_rajkbhag@quicinc.com> writes:
> From: Venkateswara Naralasetty <quic_vnaralas@quicinc.com>
>
> User can extend test mode command support to set vdev and pdev params
> for debug purpose at run time by sending vdev/pdev param set command
> through the testmode command interface.
>
> Fill the proper pdev/vdev id in driver since, pdev/vdev id details may
> not be available at user space. It will make sure that the proper
> vdev/pdev ids are sent to firmware.
>
> Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
>
> Depends-On:
> [v3,3/4] wifi: ath11k: factory test mode support
>
> Signed-off-by: Venkateswara Naralasetty <quic_vnaralas@quicinc.com>
> Signed-off-by: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>
> ---
Please add 'Depends-on' after the '---' line. This is for future
patches, no need to resend because of this.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-04-26 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 9:24 [PATCH] wifi: ath11k: update proper pdev/vdev id for testmode command Raj Kumar Bhagat
2023-04-26 7:29 ` Kalle Valo [this message]
2023-04-26 7:39 ` Raj Kumar Bhagat
2024-08-06 7:45 ` Kalle Valo
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=87a5yvt831.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rajkbhag@quicinc.com \
--cc=quic_vnaralas@quicinc.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