From: Kalle Valo <kvalo@codeaurora.org>
To: Xinming Hu <huxm@marvell.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
Brian Norris <briannorris@chromium.org>,
Dmitry Torokhov <dtor@google.com>, <rajatja@google.com>,
Zhiyuan Yang <yangzy@marvell.com>, Tim Song <songtao@marvell.com>,
Cathy Luo <cluo@marvell.com>, James Cao <jcao@marvell.com>,
Ganapathi Bhat <gbhat@marvell.com>,
Ellie Reeves <ellierevves@gmail.com>,
Xinming Hu <huxm@marvell.com>
Subject: Re: [1/3] mwifiex: make firmware mac address consistent with host configuration
Date: Mon, 30 Apr 2018 10:24:14 +0000 (UTC) [thread overview]
Message-ID: <20180430102414.C648560767@smtp.codeaurora.org> (raw)
In-Reply-To: <1524649094-20069-1-git-send-email-huxm@marvell.com>
Xinming Hu <huxm@marvell.com> wrote:
> For user configurated mac address, directly set to firmware with no change.
>
> Signed-off-by: Xinming Hu <huxm@marvell.com>
3 patches applied to wireless-drivers-next.git, thanks.
307857db47eb mwifiex: make firmware mac address consistent with host configuration
c3b2a34b82db mwifiex: always configure firmware mac address during changing virtual interface
7cce13954f0e mwifiex: keep user configured mac address during changing virtual interface
--
https://patchwork.kernel.org/patch/10362107/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-04-30 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 9:38 [PATCH 1/3] mwifiex: make firmware mac address consistent with host configuration Xinming Hu
2018-04-25 9:38 ` [PATCH 2/3] mwifiex: always configure firmware mac address during changing virtual interface Xinming Hu
2018-04-25 9:38 ` [PATCH 3/3] mwifiex: keep user configured " Xinming Hu
2018-04-30 10:24 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-04 3:02 [PATCH 1/3] mwifiex: make firmware mac address consistent with host configuration Xinming Hu
2018-04-25 8:20 ` [1/3] " 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=20180430102414.C648560767@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=cluo@marvell.com \
--cc=dtor@google.com \
--cc=ellierevves@gmail.com \
--cc=gbhat@marvell.com \
--cc=huxm@marvell.com \
--cc=jcao@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rajatja@google.com \
--cc=songtao@marvell.com \
--cc=yangzy@marvell.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).