From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [RFC 0/8] ath10k: add multi-channel support
Date: Fri, 16 Jan 2015 14:22:28 +0200 [thread overview]
Message-ID: <877fwmnce3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1420802049-11962-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 9 Jan 2015 12:14:01 +0100")
Michal Kazior <michal.kazior@tieto.com> writes:
> New wmi-tlv firmware and new hardware will support
> multi-channel operation.
>
> This prepares the driver by implementing chanctx,
> improves tx queue locking and introduces initial
> interface combinations.
>
> I'm posting this as an RFC first because I'd like
> to get some early feedback (if possible) while I
> upstream other patches this patchset is basing on.
>
>
> Michal Kazior (8):
> ath10k: defer AP self-peer removal wait
> ath10k: allow empty ssid vdev config
> ath10k: implement chanctx API
> ath10k: implement adaptive qcs command
> ath10k: protect ar->arvifs linking with data_lock
> ath10k: rework tx queue locking
> ath10k: implement tx pause wmi event
> ath10k: add proper wmi-tlv combinations
From a quick review looks good to me. Sorry for taking so long with
this.
--
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: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 0/8] ath10k: add multi-channel support
Date: Fri, 16 Jan 2015 14:22:28 +0200 [thread overview]
Message-ID: <877fwmnce3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1420802049-11962-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 9 Jan 2015 12:14:01 +0100")
Michal Kazior <michal.kazior@tieto.com> writes:
> New wmi-tlv firmware and new hardware will support
> multi-channel operation.
>
> This prepares the driver by implementing chanctx,
> improves tx queue locking and introduces initial
> interface combinations.
>
> I'm posting this as an RFC first because I'd like
> to get some early feedback (if possible) while I
> upstream other patches this patchset is basing on.
>
>
> Michal Kazior (8):
> ath10k: defer AP self-peer removal wait
> ath10k: allow empty ssid vdev config
> ath10k: implement chanctx API
> ath10k: implement adaptive qcs command
> ath10k: protect ar->arvifs linking with data_lock
> ath10k: rework tx queue locking
> ath10k: implement tx pause wmi event
> ath10k: add proper wmi-tlv combinations
>From a quick review looks good to me. Sorry for taking so long with
this.
--
Kalle Valo
next prev parent reply other threads:[~2015-01-16 12:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 11:14 [RFC 0/8] ath10k: add multi-channel support Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-09 11:14 ` [RFC 1/8] ath10k: defer AP self-peer removal wait Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-09 11:14 ` [RFC 2/8] ath10k: allow empty ssid vdev config Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-09 11:14 ` [RFC 3/8] ath10k: implement chanctx API Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-09 11:14 ` [RFC 4/8] ath10k: implement adaptive qcs command Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-09 11:14 ` [RFC 5/8] ath10k: protect ar->arvifs linking with data_lock Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-09 11:14 ` [RFC 6/8] ath10k: rework tx queue locking Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-09 11:14 ` [RFC 7/8] ath10k: implement tx pause wmi event Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-09 11:14 ` [RFC 8/8] ath10k: add proper wmi-tlv combinations Michal Kazior
2015-01-09 11:14 ` Michal Kazior
2015-01-16 12:22 ` Kalle Valo [this message]
2015-01-16 12:22 ` [RFC 0/8] ath10k: add multi-channel support 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=877fwmnce3.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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 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.