From: Kalle Valo <kvalo@codeaurora.org>
To: Xinming Hu <huxinming820@gmail.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@qca.qualcomm.com>,
Brian Norris <briannorris@google.com>,
Dmitry Torokhov <dtor@google.com>,
rajatja@google.com, Amitkumar Karwar <akarwar@marvell.com>,
Cathy Luo <cluo@marvell.com>, Xinming Hu <huxm@marvell.com>
Subject: Re: [v4, 1/4] mwifiex: remove unnecessary wakeup interrupt number sanity check
Date: Thu, 20 Apr 2017 07:18:31 +0000 (UTC) [thread overview]
Message-ID: <20170420071832.1931E6114F@smtp.codeaurora.org> (raw)
In-Reply-To: <1492066102-31251-1-git-send-email-huxinming820@gmail.com>
Xinming Hu <huxinming820@gmail.com> wrote:
> From: Xinming Hu <huxm@marvell.com>
>
> If wakeup interrupt handler is called, we know that the wakeup
> interrupt number is valid, there is no need to check it.
>
> Signed-off-by: Xinming Hu <huxm@marvell.com>
> Signed-off-by: Cathy Luo <cluo@marvell.com>
> Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
3 patches applied to wireless-drivers-next.git, thanks.
625b4dba57b2 mwifiex: remove unnecessary wakeup interrupt number sanity check
ef6c7d3cb731 mwifiex: fall back mwifiex_dbg to pr_info when adapter->dev not set
127ee1db0970 mwifiex: pcie: correct scratch register name
--
https://patchwork.kernel.org/patch/9678763/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2017-04-20 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 6:48 [PATCH v4 1/4] mwifiex: remove unnecessary wakeup interrupt number sanity check Xinming Hu
2017-04-13 6:48 ` [PATCH v4 2/4] mwifiex: fall back mwifiex_dbg to pr_info when adapter->dev not set Xinming Hu
2017-04-13 6:48 ` [PATCH v4 3/4] mwifiex: pcie: correct scratch register name Xinming Hu
2017-04-13 6:48 ` [PATCH v4 4/4] mwifiex: pcie: extract wifi part from combo firmware during function level reset Xinming Hu
2017-04-13 13:58 ` Kalle Valo
2017-04-14 4:51 ` [EXT] " Xinming Hu
2017-04-13 18:46 ` Brian Norris
2017-04-13 20:10 ` [PATCH v5 " Brian Norris
2017-04-15 9:33 ` Xinming Hu
2017-04-20 7:21 ` [v5, " Kalle Valo
2017-04-20 7:18 ` 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=20170420071832.1931E6114F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=briannorris@google.com \
--cc=cluo@marvell.com \
--cc=dtor@google.com \
--cc=huxinming820@gmail.com \
--cc=huxm@marvell.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rajatja@google.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.