From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] ath10k: fixes 2014-05-14
Date: Fri, 23 May 2014 11:01:35 +0300 [thread overview]
Message-ID: <87sio0vs80.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1400136521-11184-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 15 May 2014 08:48:39 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> This is another pair of patches.
>
> It fixes a crash recently reported by Ben, but..
>
> I've been able to find only a single code path
> that called free_irq() twice in upstream code.
> However it doesn't match the call trace reported
> by Ben. I have to assume this is related to his
> local patches or this is a very wierd case of
> recovery race between userspace/mac80211/driver.
>
> v2:
> * rebase to latest github.com/kvalo/ath-next-test
>
>
> Michal Kazior (2):
> ath10k: fix core start sequence
> ath10k: prevent hif_stop being called twice
Thanks, both patches applied.
--
Kalle Valo
prev parent reply other threads:[~2014-05-23 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 12:16 [PATCH 0/2] ath10k: fixes 2014-05-14 Michal Kazior
2014-05-14 12:16 ` [PATCH 1/2] ath10k: fix core start sequence Michal Kazior
2014-05-14 12:16 ` [PATCH 2/2] ath10k: prevent hif_stop being called twice Michal Kazior
2014-05-14 14:26 ` [PATCH 0/2] ath10k: fixes 2014-05-14 Kalle Valo
2014-05-15 6:48 ` [PATCH v2 " Michal Kazior
2014-05-15 6:48 ` [PATCH v2 1/2] ath10k: fix core start sequence Michal Kazior
2014-05-15 6:48 ` [PATCH v2 2/2] ath10k: prevent hif_stop being called twice Michal Kazior
2014-05-23 8:01 ` 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=87sio0vs80.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).