From: Brian Norris <briannorris@chromium.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: linux-wireless@vger.kernel.org, Cathy Luo <cluo@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
rajatja@google.com, briannorris@google.com,
dmitry.torokhov@gmail.com
Subject: Re: [PATCH v2 1/5] mwifiex: remove redundant condition in main process
Date: Thu, 27 Oct 2016 11:35:37 -0700 [thread overview]
Message-ID: <20161027183536.GA28717@localhost> (raw)
In-Reply-To: <1477559563-18328-1-git-send-email-akarwar@marvell.com>
On Thu, Oct 27, 2016 at 02:42:39PM +0530, Amitkumar Karwar wrote:
> This condition while calling mwifiex_check_ps_cond() is redundant.
> The function internally already takes care of it.
>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> ---
> v2: Same as v1
You've omitted the Reviewed-by tags from v1:
Reviewed-by: Brian Norris <briannorris@chromium.org>
next prev parent reply other threads:[~2016-10-27 18:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 9:12 [PATCH v2 1/5] mwifiex: remove redundant condition in main process Amitkumar Karwar
2016-10-27 9:12 ` [PATCH v2 2/5] mwifiex: use spinlock for 'mwifiex_processing' in shutdown_drv Amitkumar Karwar
2016-10-27 17:44 ` Dmitry Torokhov
2016-11-03 8:34 ` Xinming Hu
2016-11-03 16:15 ` Dmitry Torokhov
2016-11-03 18:27 ` Brian Norris
2016-11-03 18:48 ` Dmitry Torokhov
2016-11-04 3:02 ` Xinming Hu
2016-10-27 9:12 ` [PATCH v2 3/5] mwifiex: do not free firmware dump memory " Amitkumar Karwar
2016-10-27 9:12 ` [PATCH v2 4/5] mwifiex: get rid of drv_info* adapter variables Amitkumar Karwar
2016-10-27 9:12 ` [PATCH v2 5/5] mwifiex: wait firmware dump complete during card remove process Amitkumar Karwar
2016-10-27 18:48 ` Brian Norris
2016-11-16 15:27 ` Amitkumar Karwar
2016-10-27 18:35 ` Brian Norris [this message]
2016-11-03 8:04 ` [PATCH v2 1/5] mwifiex: remove redundant condition in main process Xinming Hu
2016-11-07 18:46 ` Kalle Valo
2016-11-10 19:46 ` Brian Norris
2016-11-16 13:08 ` Amitkumar Karwar
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=20161027183536.GA28717@localhost \
--to=briannorris@chromium.org \
--cc=akarwar@marvell.com \
--cc=briannorris@google.com \
--cc=cluo@marvell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.com \
--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 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).