From: Anil Duggirala <anilduggirala@fastmail.fm>
To: Kalle Valo <kvalo@codeaurora.org>,
Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: ath10k@lists.infradead.org, debian-kernel@lists.debian.org
Subject: Re: missing firmware in debian 9
Date: Wed, 28 Nov 2018 09:17:46 -0500 [thread overview]
Message-ID: <1543414666.3685745.1591818328.2D8C4AC2@webmail.messagingengine.com> (raw)
In-Reply-To: <87h8g170zl.fsf@kamboji.qca.qualcomm.com>
> It was introduced in v4.18 so once you upgrade the kernel to v4.18 or
> later you should not see the warnings anymore.
I see that I am running kernel 4.9.0-8. It may be quite some time before I get to 4.18 right?
thanks,
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-11-28 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 13:38 missing firmware in debian 9 Anil Duggirala
2018-11-26 8:48 ` Sven Eckelmann
2018-11-28 14:03 ` Kalle Valo
2018-11-28 14:17 ` Anil Duggirala [this message]
2018-11-28 14:25 ` Anil Duggirala
2018-11-28 15:17 ` Kalle Valo
2018-11-28 16:47 ` Anil Duggirala
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=1543414666.3685745.1591818328.2D8C4AC2@webmail.messagingengine.com \
--to=anilduggirala@fastmail.fm \
--cc=ath10k@lists.infradead.org \
--cc=debian-kernel@lists.debian.org \
--cc=kvalo@codeaurora.org \
--cc=sven.eckelmann@openmesh.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