From: Kalle Valo <kvalo@codeaurora.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Todd Brandt <todd.e.brandt@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
ath10k@lists.infradead.org, Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] ath10k: Drop WARN_ON()s that always trigger during system resume
Date: Fri, 01 Mar 2019 15:45:29 +0200 [thread overview]
Message-ID: <87h8cmhfnq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <3687330.FyvvPAkb64@aspire.rjw.lan> (Rafael J. Wysocki's message of "Fri, 01 Mar 2019 13:51:54 +0100")
"Rafael J. Wysocki" <rjw@rjwysocki.net> writes:
> rom: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
'F' chraracter is missing.
> ath10k_mac_vif_chan() always returns an error for the given vif
> during system-wide resume which reliably triggers two WARN_ON()s
> in ath10k_bss_info_changed() and they are not particularly
> useful in that code path, so drop them.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
And could you CC linux-wireless, please? That way the patchwork will see
it and I can take it directly from there.
--
Kalle Valo
next prev parent reply other threads:[~2019-03-01 13:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 12:51 [PATCH] ath10k: Drop WARN_ON()s that always trigger during system resume Rafael J. Wysocki
2019-03-01 13:45 ` Kalle Valo [this message]
2019-03-03 17:24 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2019-03-03 17:24 Rafael J. Wysocki
[not found] ` <2884043.Jv1Mn93hE8-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org>
2019-04-03 19:57 ` Brian Norris
[not found] ` <20190403195718.GA74723-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2019-04-03 21:44 ` Rafael J. Wysocki
[not found] ` <1645947.WPhbVaNX0l-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org>
2019-04-03 21:54 ` Brian Norris
[not found] ` <CA+ASDXPoB94o0pbY0TQGS7Dtp2RNz=3goH38gpLtBoJ15i7eoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-04-04 4:06 ` Kalle Valo
[not found] ` <87k1gatnvt.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2019-04-04 8:28 ` Rafael J. Wysocki
2019-04-26 7:18 ` Kalle Valo
2019-04-26 7:18 ` Kalle Valo
[not found] ` <87o94tutdz.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2019-04-29 8:48 ` Rafael J. Wysocki
2019-04-29 8:48 ` Rafael J. Wysocki
[not found] ` <CAJZ5v0ifD=DATprUeeO2_LGs04aEEhPB6AcGVPxWUdQaOma+ww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-04-29 10:41 ` Claire Chang
2019-04-29 10:41 ` Claire Chang
[not found] ` <CALiNf2_qV+iViHbS0tQquTMZfu6XfFvQCH14mdT5bixn94DZ2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-04-29 14:12 ` Kalle Valo
2019-04-29 14:12 ` Kalle Valo
2019-04-29 14:10 ` Kalle Valo
2019-04-29 14:10 ` Kalle Valo
2019-04-29 14:26 ` Kalle Valo
2019-04-29 14:26 ` Kalle Valo
2019-04-29 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=87h8cmhfnq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=todd.e.brandt@intel.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;
as well as URLs for NNTP newsgroup(s).