From: Wen Gong <wgong@qti.qualcomm.com>
To: Brian Norris <briannorris@chromium.org>
Cc: "Michał Kazior" <kazikcz@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"Wen Gong" <wgong@codeaurora.org>
Subject: RE: [PATCH] ath10k: Remove ATH10K_STATE_RESTARTED in simulate fw crash
Date: Tue, 28 May 2019 02:49:30 +0000 [thread overview]
Message-ID: <301c4b127ea74abd8a9d8221d93656fd@aptaiexm02f.ap.qualcomm.com> (raw)
In-Reply-To: <b073fa90e9a3437c9846ce2d22fab15f@aptaiexm02f.ap.qualcomm.com>
> -----Original Message-----
> From: ath10k <ath10k-bounces@lists.infradead.org> On Behalf Of Wen Gong
> Sent: Wednesday, April 10, 2019 10:45 AM
> To: Brian Norris <briannorris@chromium.org>
> Cc: Michał Kazior <kazikcz@gmail.com>; linux-wireless <linux-
> wireless@vger.kernel.org>; ath10k@lists.infradead.org; Wen Gong
> <wgong@codeaurora.org>
> Subject: [EXT] RE: [PATCH] ath10k: Remove ATH10K_STATE_RESTARTED in
> simulate fw crash
>
> If ChromeOS is easy to change tool,
> I think I will change the mechanism of the simulate_fw_crash.
> Then all tools will work normally.
>
New patch uploaded
https://patchwork.kernel.org/patch/10897587/
[v2] ath10k: Remove ATH10K_STATE_RESTARTED in simulate fw crash
prev parent reply other threads:[~2019-05-28 2:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 2:50 [PATCH] ath10k: Remove ATH10K_STATE_RESTARTED in simulate fw crash Wen Gong
2018-11-14 7:48 ` Michał Kazior
2019-01-07 7:16 ` Wen Gong
2019-01-07 8:35 ` Michał Kazior
2019-01-08 8:45 ` Wen Gong
2019-02-08 13:32 ` Kalle Valo
2019-02-08 13:34 ` Kalle Valo
2019-04-01 6:11 ` Wen Gong
2019-04-08 10:19 ` Wen Gong
2019-04-08 17:27 ` Michał Kazior
2019-04-09 5:09 ` Wen Gong
2019-04-09 23:25 ` Brian Norris
2019-04-10 2:45 ` Wen Gong
2019-05-28 2:49 ` Wen Gong [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=301c4b127ea74abd8a9d8221d93656fd@aptaiexm02f.ap.qualcomm.com \
--to=wgong@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=kazikcz@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wgong@codeaurora.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;
as well as URLs for NNTP newsgroup(s).