ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Bruno Antunes <baantunes@gmail.com>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	voncken <cedric.voncken@acksys.fr>
Subject: Re: [OpenWrt-Devel] ATH10K VLAN firmware issue
Date: Tue, 15 Nov 2016 13:43:38 +0000	[thread overview]
Message-ID: <87polwq2nq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CABUTiXV8eFsW4MJET4spvjVQvFgi66NV7hLLxFC6Ttqs1znxjA@mail.gmail.com>	(Bruno Antunes's message of "Mon, 7 Nov 2016 18:40:37 +0000")

Bruno Antunes <baantunes@gmail.com> writes:

> On 7 November 2016 at 18:06, Valo, Kalle <kvalo@qca.qualcomm.com> wrote:
>> Bruno Antunes <baantunes@gmail.com> writes:
>>
>>> On 4 November 2016 at 21:17, Valo, Kalle <kvalo@qca.qualcomm.com> wrote:
>>>
>>>> Can someone file a bug to bugzilla about this so that all the info is
>>>> properly stored? The more comprehensive the report is the better.
>>>>
>>>> https://bugzilla.kernel.org/
>>>
>>> I will file a bug report.
>>
>> Thanks, it's good to store all in one place so that it's easier to find
>> the relevant info.
>
> Just file the bug with the ID 187241 - VLAN support in ATH10k Feel
> free to ask for adicional info. I did not mention any names in the bug
> report fell free to take credit if wanted.

Thanks. I'll report it to the firmware team, let's see what happens. If
there's more information which might help to fix this feel free to
update that to the bug report.

https://bugzilla.kernel.org/show_bug.cgi?id=187241

-- 
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2016-11-15 13:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 14:29 ATH10K VLAN firmware issue Cedric VONCKEN
2015-12-09 15:33 ` Ben Greear
2015-12-09 17:24   ` voncken
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 17:28           ` yu-chieh kung
2016-11-04 21:50             ` Ben Greear
2016-11-04 22:23               ` Ben Greear
2016-11-05  8:05                 ` Sebastian Gottschall
2016-11-05 14:35                   ` Ben Greear
2016-11-15 14:37                     ` voncken
2016-11-15 14:55                       ` Ben Greear
2016-11-15 15:00                         ` Bruno Antunes
2016-11-15 15:06                           ` Ben Greear
2016-11-07 11:54                 ` Bruno Antunes
2016-11-07 14:06                   ` Ben Greear
2016-11-07 14:13                     ` Bruno Antunes
2016-11-04 21:17       ` Valo, Kalle
2016-11-07 12:01         ` Bruno Antunes
2016-11-07 18:06           ` Valo, Kalle
2016-11-07 18:40             ` [OpenWrt-Devel] " Bruno Antunes
2016-11-15 13:43               ` Valo, Kalle [this message]
2016-11-15 14:53                 ` Bruno Antunes
2017-02-21 12:59                 ` voncken
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-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=87polwq2nq.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=baantunes@gmail.com \
    --cc=cedric.voncken@acksys.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox