From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: ath11k@lists.infradead.org, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH ath-next 0/2] wifi: ath: fix stride mismatch in mac_phy_caps_parse
Date: Wed, 29 Jul 2026 08:29:40 -0700 [thread overview]
Message-ID: <a0cc20a1-82c6-48bf-922a-dc7470663574@oss.qualcomm.com> (raw)
In-Reply-To: <20260729-mac_phy_caps_parse-stride-mismatch-v1-0-077a1a0c50d8@oss.qualcomm.com>
On 7/29/2026 8:26 AM, Jeff Johnson wrote:
> Both ath11k and ath12k have the same issue.
>
> ---
> Jeff Johnson (2):
> wifi: ath12k: fix stride mismatch in mac_phy_caps_parse()
> wifi: ath11k: fix stride mismatch in mac_phy_caps_parse()
>
> drivers/net/wireless/ath/ath11k/wmi.c | 8 +++++---
> drivers/net/wireless/ath/ath12k/wmi.c | 8 +++++---
> 2 files changed, 10 insertions(+), 6 deletions(-)
> ---
> base-commit: 189721a4afa1804315e7dcfca9ca0539c7b1d7af
> change-id: 20260720-mac_phy_caps_parse-stride-mismatch-e7292580f072
>
<sigh> ignore this repost. invoked the wrong maintainer script...
next prev parent reply other threads:[~2026-07-29 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 15:26 Jeff Johnson
2026-07-29 15:26 ` [PATCH ath-next 1/2] wifi: ath12k: fix stride mismatch in mac_phy_caps_parse() Jeff Johnson
2026-07-29 15:26 ` [PATCH ath-next 2/2] wifi: ath11k: " Jeff Johnson
2026-07-29 15:29 ` Jeff Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-29 1:05 [PATCH ath-next 0/2] wifi: ath: fix stride mismatch in mac_phy_caps_parse Jeff Johnson
2026-07-29 3:57 ` Rameshkumar Sundaram
2026-07-29 9:00 ` Baochen Qiang
2026-07-30 15:10 ` 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=a0cc20a1-82c6-48bf-922a-dc7470663574@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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
all inboxes | Powered by JetHome®