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/6] ath10k: ath10k: fixes 2014-08-07, part 2
Date: Mon, 25 Aug 2014 11:30:17 +0300 [thread overview]
Message-ID: <8738cl6kfa.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1408710214-24894-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 22 Aug 2014 14:23:28 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Hi,
>
> This is part 2 (of 3) of my patches. Split for
> your reviewing pleasure.
>
> This is related to irq handling only. Prepares for
> more start/restart sequences fixes.
>
> v2:
> * patch [1/6] is from part 1
> * patch [5/6] is new
> * some fixes, see notes
> * based on
> f2c7cb774e3e0a8152b1134015c245ba0abddfc6 and
> 4 crash dump patches (v8) from Kalle
>
>
> Michal Kazior (6):
> ath10k: move fw init print
> ath10k: fix legacy irq workaround
> ath10k: setup irq method in probe
> ath10k: split ce irq/handler setup
> ath10k: make sure to really disable irqs
> ath10k: remove early irq handling
Thanks, all six patches applied.
--
Kalle Valo
prev parent reply other threads:[~2014-08-25 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 12:23 [PATCH v2 0/6] ath10k: ath10k: fixes 2014-08-07, part 2 Michal Kazior
2014-08-22 12:23 ` [PATCH v2 1/6] ath10k: move fw init print Michal Kazior
2014-08-22 12:23 ` [PATCH v2 2/6] ath10k: fix legacy irq workaround Michal Kazior
2014-08-22 12:23 ` [PATCH v2 3/6] ath10k: setup irq method in probe Michal Kazior
2014-08-22 12:23 ` [PATCH v2 4/6] ath10k: split ce irq/handler setup Michal Kazior
2014-08-22 12:23 ` [PATCH v2 5/6] ath10k: make sure to really disable irqs Michal Kazior
2014-08-22 12:23 ` [PATCH v2 6/6] ath10k: remove early irq handling Michal Kazior
2014-08-22 12:42 ` [PATCH v2 0/6] ath10k: ath10k: fixes 2014-08-07, part 2 Michal Kazior
2014-08-25 8:30 ` 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=8738cl6kfa.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).