From: Kalle Valo <kvalo@codeaurora.org>
To: "Machani, Yaniv" <yanivma@ti.com>
Cc: <linux-kernel@vger.kernel.org>, Maital Hahn <maitalm@ti.com>,
Yaniv Machani <yanivma@ti.com>, Eliad Peller <eliad@wizery.com>,
Guy Mishol <guym@ti.com>, Johannes Berg <johannes.berg@intel.com>,
Arik Nemtsov <arik@wizery.com>, <linux-wireless@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: wlcore/wl18xx: mesh: added initial mesh support for wl8
Date: Mon, 18 Jul 2016 19:33:47 +0000 (UTC) [thread overview]
Message-ID: <20160718193347.4F5CD602A9@smtp.codeaurora.org> (raw)
In-Reply-To: <20160628104305.4533-1-yanivma@ti.com>
"Machani, Yaniv" <yanivma@ti.com> wrote:
> From: Maital Hahn <maitalm@ti.com>
>
> 1. Added support for interface and role of mesh type.
> 2. Enabled enable/start of mesh-point role,
> and opening and closing a connection with a mesh peer.
> 3. Added multirole combination of mesh and ap
> under the same limits of dual ap mode.
> 4. Add support for 'sta_rc_update' opcode for mesh IF.
> The 'sta_rc_update' opcode is being used in mesh_plink.c.
> Add support in wlcore to handle this opcode correctly for mesh
> (as opposed to current implementation that handles STA only).
> 5. Bumped the firmware version to support new Mesh functionality
>
> Signed-off-by: Maital Hahn <maitalm@ti.com>
> Signed-off-by: Yaniv Machani <yanivma@ti.com>
Thanks, 1 patch applied to wireless-drivers-next.git:
c0174ee28003 wlcore/wl18xx: mesh: added initial mesh support for wl8
--
Sent by pwcli
https://patchwork.kernel.org/patch/9202707/
prev parent reply other threads:[~2016-07-18 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 10:41 [PATCH] wlcore/wl18xx: mesh: added initial mesh support for wl8 Yaniv Machani
2016-07-13 9:53 ` Machani, Yaniv
2016-07-14 12:04 ` Kalle Valo
2016-07-18 17:42 ` Kalle Valo
2016-07-18 18:27 ` Machani, Yaniv
2016-07-18 19:33 ` Kalle Valo [this message]
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=20160718193347.4F5CD602A9@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arik@wizery.com \
--cc=eliad@wizery.com \
--cc=guym@ti.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maitalm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=yanivma@ti.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;
as well as URLs for NNTP newsgroup(s).