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: [v5, 1/3] mwifiex: refactor device dump code to make it generic for usb interface
Date: Mon, 8 Jan 2018 17:37:55 +0000 (UTC) [thread overview]
Message-ID: <20180108173755.B25B260215@smtp.codeaurora.org> (raw)
In-Reply-To: <1513064293-9400-1-git-send-email-huxm@marvell.com>
Xinming Hu <huxm@marvell.com> wrote:
> This patch refactor current device dump code to make it generic
> for subsequent implementation on usb interface.
>
> Signed-off-by: Xinming Hu <huxm@marvell.com>
> Signed-off-by: Cathy Luo <cluo@marvell.com>
> Signed-off-by: Ganapathi Bhat <gbhat@marvell.com>
3 patches applied to wireless-drivers-next.git, thanks.
d0e2b44ef328 mwifiex: refactor device dump code to make it generic for usb interface
f5ecd02a8b20 mwifiex: device dump support for usb interface
18d605013357 mwifiex: debugfs: trigger device dump for usb interface
--
https://patchwork.kernel.org/patch/10106407/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-01-08 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 7:38 [PATCH v5 1/3] mwifiex: refactor device dump code to make it generic for usb interface Xinming Hu
2017-12-12 7:38 ` [PATCH v5 2/3] mwifiex: device dump support " Xinming Hu
2017-12-12 7:38 ` [PATCH v5 3/3] mwifiex: debugfs: trigger device dump " Xinming Hu
2018-01-08 17:37 ` 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=20180108173755.B25B260215@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 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.