All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: Avinash Patil <patila@marvell.com>, Cathy Luo <cluo@marvell.com>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mwifiex: check driver status in connect and scan handlers
Date: Thu, 22 Jan 2015 16:13:23 +0200	[thread overview]
Message-ID: <87lhkunbss.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5FF020A1CFFEEC49BD1E09530C4FF5951B1633A3FA@SC-VEXCH1.marvell.com> (Amitkumar Karwar's message of "Sat, 17 Jan 2015 05:05:25 -0800")

Amitkumar Karwar <akarwar@marvell.com> writes:

> Hi Kalle,
>
>>On Wed, Jan 7, 2015 at 5:27 PM, Amitkumar Karwar <akarwar@marvell.com> wrote:
>>Ignore scan and connection requests from cfg80211 when driver
>>unload is in process or previous command has timed out due to
>>a firmware bug. This patch fixes corner case system crash
>>issues.
>
>>Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
>>Signed-off-by: Cathy Luo <cluo@marvell.com>
>>---
>> drivers/net/wireless/mwifiex/cfg80211.c | 8 ++++++++
>> drivers/net/wireless/mwifiex/scan.c     | 6 ++++++
>> 2 files changed, 14 insertions(+)
>
> Could you please check this patch? Let me know if you want me to
> resend it.

Unfortunately I'm lagging behind because I decided to work on automating
the patch handling. I'm hoping that makes it easier for me to stay
up-to-date.

Also it would help me that instead of mailing me people would check the
status from the patchwork:

https://patchwork.kernel.org/project/linux-wireless/list/

If the patch is delegated to me and state is one of "New", "Under
Review" or "Awaiting Upstream" it means that the patch is in queue of
patches to process. If it's anything else it means that the patch is
dropped due to some reason, either for a reason (issues found during
review etc) or accidentally (which can also happen in rare cases).

This patch is in 'Under Review' state so I will get to it eventually:

https://patchwork.kernel.org/patch/5584351/

And even looks to be in top of my list so it shouldn't take long.

-- 
Kalle Valo

  reply	other threads:[~2015-01-22 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 11:57 [PATCH] mwifiex: check driver status in connect and scan handlers Amitkumar Karwar
     [not found] ` <CAEhWJFnr28=Q4TFwzwcNoWPQRbUY0+mWu8nbocs3789v8X1PHw@mail.gmail.com>
2015-01-17 13:05   ` Amitkumar Karwar
2015-01-22 14:13     ` Kalle Valo [this message]
2015-01-23  3:49       ` Amitkumar Karwar
2015-01-23 17:03 ` 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=87lhkunbss.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=patila@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.