From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Julius Bairaktaris <julius@bairaktaris.de>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: jjohnson@kernel.org, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
vasanthakumar.thiagarajan@oss.qualcomm.com,
rameshkumar.sundaram@oss.qualcomm.com
Subject: Re: [PATCH ath-next v2 2/2] wifi: ath11k: disable interrupts during firmware crash recovery
Date: Mon, 21 Sep 2026 11:17:10 +0800 [thread overview]
Message-ID: <358d7dd0-20b0-44ee-8b1e-a0cc6cb40abe@oss.qualcomm.com> (raw)
In-Reply-To: <CAC1t37Ltrh+BBaEPi8grXnMrDt3qGDH8BA56av-h7=yPCCk0Nw@mail.gmail.com>
On 9/21/2026 12:42 AM, Julius Bairaktaris wrote:
> Hi @Baochen,
>
> tested 5 times and it solves the problem. Thanks!
Thanks. Can I have below tag when I submit the fix ?
Tested-by: Julius Bairaktaris <julius@bairaktaris.de>
next prev parent reply other threads:[~2026-09-21 3:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 22:19 [PATCH ath-next v2 0/2] wifi: ath11k: fix SoC reboot on firmware crash on AHB Julius Bairaktaris
2026-07-26 22:19 ` [PATCH ath-next v2 1/2] wifi: ath11k: implement CE interrupt enable/disable for AHB Julius Bairaktaris
2026-07-26 22:19 ` [PATCH ath-next v2 2/2] wifi: ath11k: disable interrupts during firmware crash recovery Julius Bairaktaris
[not found] ` <CGME20260911075315eucas1p1b4ffb1f57ef187e0a055072ccc0983e3@eucas1p1.samsung.com>
2026-09-11 7:53 ` Marek Szyprowski
2026-09-11 16:54 ` Jeff Johnson
2026-09-14 6:32 ` Baochen Qiang
2026-09-14 6:47 ` Julius Bairaktaris
2026-09-14 7:22 ` Marek Szyprowski
2026-09-20 16:42 ` Julius Bairaktaris
2026-09-21 3:17 ` Baochen Qiang [this message]
2026-09-21 6:32 ` Julius Bairaktaris
2026-07-31 3:07 ` [PATCH ath-next v2 0/2] wifi: ath11k: fix SoC reboot on firmware crash on AHB Baochen Qiang
2026-08-05 10:48 ` Julius Bairaktaris
2026-08-05 11:13 ` Rameshkumar Sundaram
2026-09-03 19:02 ` 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=358d7dd0-20b0-44ee-8b1e-a0cc6cb40abe@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=julius@bairaktaris.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rameshkumar.sundaram@oss.qualcomm.com \
--cc=vasanthakumar.thiagarajan@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
all inboxes | Powered by JetHome®