From: "Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
Mohammed Shafi Shajakhan <mohammed@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH v3] ath10k: Fix crash during rmmod when probe firmware fails
Date: Fri, 10 Feb 2017 12:16:42 +0000 [thread overview]
Message-ID: <1486729001850.80243@qti.qualcomm.com> (raw)
In-Reply-To: <87lgteidii.fsf@kamboji.qca.qualcomm.com>
Mohammed Shafi Shajakhan <mohammed@codeaurora.org> writes:
> the change suggested by you helps, and the device probe, scan
> is successful as well. Still good to have this change part of your
> basic sanity and regression testing !
Sure. I was sort of expecting that you would send v4 but I haven't seen
one so I guess you assumed I send that? :) I'll then submit v4.
[shafi] thanks Kalle, just saw your patch.
regards,
shafi
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: "Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
Mohammed Shafi Shajakhan <mohammed@codeaurora.org>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3] ath10k: Fix crash during rmmod when probe firmware fails
Date: Fri, 10 Feb 2017 12:16:42 +0000 [thread overview]
Message-ID: <1486729001850.80243@qti.qualcomm.com> (raw)
In-Reply-To: <87lgteidii.fsf@kamboji.qca.qualcomm.com>
Mohammed Shafi Shajakhan <mohammed@codeaurora.org> writes:=0A=
=0A=
> the change suggested by you helps, and the device probe, scan=0A=
> is successful as well. Still good to have this change part of your=0A=
> basic sanity and regression testing !=0A=
=0A=
Sure. I was sort of expecting that you would send v4 but I haven't seen=0A=
one so I guess you assumed I send that? :) I'll then submit v4.=0A=
=0A=
[shafi] thanks Kalle, just saw your patch.=0A=
=0A=
regards,=0A=
shafi=0A=
next prev parent reply other threads:[~2017-02-10 12:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 8:09 [PATCH v3] ath10k: Fix crash during rmmod when probe firmware fails Mohammed Shafi Shajakhan
2016-12-20 8:09 ` Mohammed Shafi Shajakhan
2017-01-25 13:29 ` Valo, Kalle
2017-01-25 13:29 ` Valo, Kalle
2017-01-25 13:46 ` Valo, Kalle
2017-01-25 13:46 ` Valo, Kalle
2017-02-06 6:02 ` Mohammed Shafi Shajakhan
2017-02-06 6:02 ` Mohammed Shafi Shajakhan
2017-02-06 10:04 ` Mohammed Shafi Shajakhan
2017-02-06 10:04 ` Mohammed Shafi Shajakhan
2017-02-06 12:16 ` Michael Ney
2017-02-06 12:16 ` Michael Ney
2017-02-06 12:21 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2017-02-06 12:21 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2017-02-10 9:47 ` Valo, Kalle
2017-02-10 9:47 ` Valo, Kalle
2017-02-10 11:36 ` Valo, Kalle
2017-02-10 11:36 ` Valo, Kalle
2017-02-10 12:16 ` Shajakhan, Mohammed Shafi (Mohammed Shafi) [this message]
2017-02-10 12:16 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
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=1486729001850.80243@qti.qualcomm.com \
--to=mohammed@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed@codeaurora.org \
/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.