From: Kalle Valo <kvalo@codeaurora.org>
To: Youghandhar Chintala <youghand@codeaurora.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
linux-kernel@vger.kernel.org, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Abhishek Kumar <kuabhs@chromium.org>,
Steev Klimaszewski <steev@kali.org>,
Matthias Kaehlcke <mka@chromium.org>,
Rakesh Pillai <pillair@codeaurora.org>
Subject: Re: [PATCH v3] ath10k: Don't always treat modem stop events as crashes
Date: Fri, 24 Sep 2021 18:17:49 +0300 [thread overview]
Message-ID: <871r5eroiq.fsf@codeaurora.org> (raw)
In-Reply-To: <98706efc03c88b54bfb44161566c8e4b@codeaurora.org> (Youghandhar Chintala's message of "Fri, 24 Sep 2021 18:13:48 +0530")
Youghandhar Chintala <youghand@codeaurora.org> writes:
> I pulled the latest patch changes and tested them on SC7180. Which
> works as expected.
> Do not see this error message during reboot and can be seen while
> doing SSR.
>
> Tested-By: Youghandhar Chintala <youghand@codeaurora.org>
Thanks for testing. But this style of replies makes it hard to use
patchwork:
https://patchwork.kernel.org/project/linux-wireless/patch/20210922233341.182624-1-swboyd@chromium.org/
So please do not top post and always edit your quotes, thank you, Same
request also to Rakesh.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-09-24 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 23:33 [PATCH v3] ath10k: Don't always treat modem stop events as crashes Stephen Boyd
2021-09-24 12:38 ` pillair
2021-09-24 12:43 ` Youghandhar Chintala
2021-09-24 15:17 ` Kalle Valo [this message]
2021-10-05 14:26 ` 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=871r5eroiq.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kuabhs@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=pillair@codeaurora.org \
--cc=steev@kali.org \
--cc=swboyd@chromium.org \
--cc=youghand@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).