From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
<ath10k@lists.infradead.org>
Subject: Re: [PATCH 0/7] ath10k: fixes 2013-10-15
Date: Wed, 16 Oct 2013 17:18:15 +0300 [thread overview]
Message-ID: <8738o17108.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQ=wpEWF3sWavKSfKy4s6qW097amCt_VqbapZg-ECWOE=g@mail.gmail.com> (Michal Kazior's message of "Wed, 16 Oct 2013 07:05:56 -0700")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 16 October 2013 05:56, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Kalle Valo <kvalo@qca.qualcomm.com> writes:
>>
>> Michal, if it's ok for you I'll submit v2 of this patchset. I'll fix the
>> long line warnings and also I do small cleanup to the warm reset code.
>
> I am totally okay with this. Thank you for your trouble.
As you can see, I changed the warm reset code quite a lot. If you have
time, please review that carefully.
--
Kalle Valo
prev parent reply other threads:[~2013-10-16 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 17:29 [PATCH 0/7] ath10k: fixes 2013-10-15 Michal Kazior
2013-10-15 17:29 ` [PATCH 1/7] ath10k: prevent starting monitor without a vdev Michal Kazior
2013-10-15 17:29 ` [PATCH 2/7] ath10k: add sanity checks for monitor management Michal Kazior
2013-10-16 9:19 ` Kalle Valo
2013-10-15 17:29 ` [PATCH 3/7] ath10k: fix endianess in prints Michal Kazior
2013-10-15 17:29 ` [PATCH 4/7] ath10k: fix NSS reporting in RX Michal Kazior
2013-10-15 17:29 ` [PATCH 5/7] ath10k: fix NULL deref upon early FW crash Michal Kazior
2013-10-15 17:29 ` [PATCH 6/7] ath10k: fix device initialization routine Michal Kazior
2013-10-16 13:31 ` Kalle Valo
2013-10-15 17:29 ` [PATCH 7/7] ath10k: fix FW crashes on heavy TX on 10.1.389 AP FW Michal Kazior
2013-10-15 18:55 ` [PATCH 0/7] ath10k: fixes 2013-10-15 Kalle Valo
2013-10-16 12:56 ` Kalle Valo
2013-10-16 14:05 ` Michal Kazior
2013-10-16 14:18 ` 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=8738o17108.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