From: "Machani, Yaniv" <yanivma@ti.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kalle Valo <kvalo@codeaurora.org>
Cc: "Hahn, Maital" <maitalm@ti.com>, Eliad Peller <eliad@wizery.com>,
"Mishol, Guy" <guym@ti.com>,
Johannes Berg <johannes.berg@intel.com>,
"Arik Nemtsov" <arik@wizery.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH] wlcore/wl18xx: mesh: added initial mesh support for wl8
Date: Wed, 13 Jul 2016 09:53:35 +0000 [thread overview]
Message-ID: <AE1C82FB3D0EC64DB1F752C81CBD1101391FC336@DFRE01.ent.ti.com> (raw)
In-Reply-To: <20160628104305.4533-1-yanivma@ti.com>
On Tue, Jun 28, 2016 at 13:41:35, Machani, Yaniv wrote:
> Guy; Johannes Berg; Arik Nemtsov; linux-wireless@vger.kernel.org;
> netdev@vger.kernel.org
> Subject: [PATCH] wlcore/wl18xx: mesh: added initial mesh support for
> wl8
>
> 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>
> ---
Any comments on this patch ?
Can this be pulled ?
Thanks,
Yaniv
next prev parent reply other threads:[~2016-07-13 9:53 UTC|newest]
Thread overview: 8+ 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 [this message]
2016-07-14 12:04 ` Kalle Valo
2016-07-18 17:42 ` Kalle Valo
2016-07-18 18:27 ` Machani, Yaniv
2016-07-18 18:27 ` Machani, Yaniv
2016-07-18 19:33 ` Kalle Valo
2016-07-18 19:33 ` 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=AE1C82FB3D0EC64DB1F752C81CBD1101391FC336@DFRE01.ent.ti.com \
--to=yanivma@ti.com \
--cc=arik@wizery.com \
--cc=eliad@wizery.com \
--cc=guym@ti.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maitalm@ti.com \
--cc=netdev@vger.kernel.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.