From: "voncken" <cedric.voncken@acksys.fr>
To: "'Valo, Kalle'" <kvalo@qca.qualcomm.com>
Cc: 'OpenWrt Development List' <openwrt-devel@lists.openwrt.org>,
'linux-wireless' <linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org
Subject: RE: [OpenWrt-Devel] ATH10K VLAN firmware issue
Date: Wed, 22 Feb 2017 14:55:09 +0100 [thread overview]
Message-ID: <02ef01d28d13$48181ac0$d8485040$@acksys.fr> (raw)
In-Reply-To: <87efyrd6lv.fsf@kamboji.qca.qualcomm.com>
Thanks for your answer,
How I can know when this issue will be fixed in ath10k firmware
mainline?
Do you know if Qualcomm publish a release note for this firmware?
> -----Message d'origine-----
> De : linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-
> owner@vger.kernel.org] De la part de Valo, Kalle
> Envoyé : mardi 21 février 2017 14:19
> À : voncken
> Cc : 'OpenWrt Development List'; 'linux-wireless';
> ath10k@lists.infradead.org
> Objet : Re: [OpenWrt-Devel] ATH10K VLAN firmware issue
>
> voncken <cedric.voncken@acksys.fr> writes:
>
> > Do you know if the firmware team planned to fix the VLAN issue on
> > ath10k firmware?
>
> I reported it forward only this week.
>
> --
> Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: "voncken" <cedric.voncken@acksys.fr>
To: "'Valo, Kalle'" <kvalo@qca.qualcomm.com>
Cc: "'OpenWrt Development List'" <openwrt-devel@lists.openwrt.org>,
"'linux-wireless'" <linux-wireless@vger.kernel.org>,
<ath10k@lists.infradead.org>
Subject: RE: [OpenWrt-Devel] ATH10K VLAN firmware issue
Date: Wed, 22 Feb 2017 14:55:09 +0100 [thread overview]
Message-ID: <02ef01d28d13$48181ac0$d8485040$@acksys.fr> (raw)
In-Reply-To: <87efyrd6lv.fsf@kamboji.qca.qualcomm.com>
Thanks for your answer,
How I can know when this issue will be fixed in ath10k firmware
mainline?
Do you know if Qualcomm publish a release note for this firmware?
> -----Message d'origine-----
> De : linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-
> owner@vger.kernel.org] De la part de Valo, Kalle
> Envoyé : mardi 21 février 2017 14:19
> À : voncken
> Cc : 'OpenWrt Development List'; 'linux-wireless';
> ath10k@lists.infradead.org
> Objet : Re: [OpenWrt-Devel] ATH10K VLAN firmware issue
>
> voncken <cedric.voncken@acksys.fr> writes:
>
> > Do you know if the firmware team planned to fix the VLAN issue on
> > ath10k firmware?
>
> I reported it forward only this week.
>
> --
> Kalle Valo
next prev parent reply other threads:[~2017-02-22 16:25 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 14:29 ATH10K VLAN firmware issue Cedric VONCKEN
2015-12-08 14:29 ` Cedric VONCKEN
2015-12-09 15:33 ` Ben Greear
2015-12-09 15:33 ` Ben Greear
2015-12-09 17:24 ` voncken
2015-12-09 17:24 ` voncken
2016-11-04 14:13 ` Bruno Antunes
2016-11-04 14:13 ` Bruno Antunes
[not found] ` <27f802e7-79c5-a17f-1883-88e62a6520ef@ezplanet.net>
2016-11-04 14:41 ` [OpenWrt-Devel] " Bruno Antunes
2016-11-04 14:41 ` Bruno Antunes
2016-11-04 17:28 ` yu-chieh kung
2016-11-04 17:28 ` yu-chieh kung
2016-11-04 21:50 ` Ben Greear
2016-11-04 21:50 ` Ben Greear
2016-11-04 22:23 ` Ben Greear
2016-11-04 22:23 ` Ben Greear
2016-11-05 8:05 ` Sebastian Gottschall
2016-11-05 8:05 ` Sebastian Gottschall
2016-11-05 14:35 ` Ben Greear
2016-11-05 14:35 ` Ben Greear
2016-11-15 14:37 ` voncken
2016-11-15 14:37 ` voncken
2016-11-15 14:55 ` Ben Greear
2016-11-15 14:55 ` Ben Greear
2016-11-15 15:00 ` Bruno Antunes
2016-11-15 15:00 ` Bruno Antunes
2016-11-15 15:06 ` Ben Greear
2016-11-15 15:06 ` Ben Greear
2016-11-07 11:54 ` Bruno Antunes
2016-11-07 11:54 ` Bruno Antunes
2016-11-07 14:06 ` Ben Greear
2016-11-07 14:06 ` Ben Greear
2016-11-07 14:13 ` Bruno Antunes
2016-11-07 14:13 ` Bruno Antunes
2016-11-04 21:17 ` Valo, Kalle
2016-11-04 21:17 ` Valo, Kalle
2016-11-07 12:01 ` Bruno Antunes
2016-11-07 12:01 ` Bruno Antunes
2016-11-07 18:06 ` Valo, Kalle
2016-11-07 18:06 ` Valo, Kalle
2016-11-07 18:40 ` [OpenWrt-Devel] " Bruno Antunes
2016-11-07 18:40 ` Bruno Antunes
2016-11-15 13:43 ` Valo, Kalle
2016-11-15 13:43 ` Valo, Kalle
2016-11-15 14:53 ` Bruno Antunes
2016-11-15 14:53 ` Bruno Antunes
2017-02-21 12:59 ` voncken
2017-02-21 12:59 ` voncken
2017-02-21 13:19 ` Valo, Kalle
2017-02-21 13:19 ` Valo, Kalle
[not found] ` <CAKR_QVLpSWab-kF-f8=xqw+oWAfA966GDm7CtXrWfzmJz8gP-w@mail.gmail.com>
2017-02-21 16:47 ` Bruno Antunes
2017-02-21 16:47 ` Bruno Antunes
2017-02-22 13:55 ` voncken [this message]
2017-02-22 13:55 ` voncken
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='02ef01d28d13$48181ac0$d8485040$@acksys.fr' \
--to=cedric.voncken@acksys.fr \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.