From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Brian Norris <briannorris@chromium.org>
Cc: Ryan Hsu <ryanhsu@qti.qualcomm.com>,
Grant Grundler <grundler@chromium.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"michal.kazior@tieto.com" <michal.kazior@tieto.com>
Subject: Re: [PATCH] ath10k: fix core PCI suspend when WoWLAN is supported but disabled
Date: Thu, 12 Oct 2017 03:58:00 +0000 [thread overview]
Message-ID: <87y3ohow54.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20171012003805.GA89253@google.com> (Brian Norris's message of "Wed, 11 Oct 2017 17:38:06 -0700")
Brian Norris <briannorris@chromium.org> writes:
> Ping? Any comments? I know there's more than one way to slice this
> problem, but it's most definitely a problem...
I'm lagging behind with patches but I'll try to catch up this week.
Sorry.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-10-12 3:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 23:24 [PATCH] ath10k: fix core PCI suspend when WoWLAN is supported but disabled Brian Norris
2017-10-12 0:38 ` Brian Norris
2017-10-12 0:43 ` Adrian Chadd
2017-10-12 3:58 ` Kalle Valo [this message]
2017-10-13 11:37 ` Kalle Valo
2017-10-19 14:32 ` Kalle Valo
2017-10-19 17:12 ` Brian Norris
2017-10-19 18:45 ` [PATCH] ath10k: fix build errors with !CONFIG_PM Brian Norris
2017-10-20 6:29 ` Kalle Valo
2017-10-27 13:44 ` Kalle Valo
2017-10-20 6:24 ` ath10k: fix core PCI suspend when WoWLAN is supported but disabled 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=87y3ohow54.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=grundler@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=ryanhsu@qti.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