From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 2/2] ath10k: refactor scan locking
Date: Mon, 22 Apr 2013 11:15:57 +0300 [thread overview]
Message-ID: <87k3nvkmki.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5174F0D8.3060602@tieto.com> (Michal Kazior's message of "Mon, 22 Apr 2013 10:12:08 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 22/04/13 10:08, Kalle Valo wrote:
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>> Since we have data_lock it is no longer necessary
>>> to have scan.lock.
>>>
>>> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
>>> ---
>>
>> [...]
>>
>>> ret = ath10k_wmi_stop_scan(ar, &arg);
>>> if (ret)
>>> ath10k_warn("%s: ath10k_wmi_stop_scan failed (%d)\n", __func__, ret);
>>>
>>> + ath10k_wmi_flush_tx(ar);
>>
>> Is this by accident?
>
> Oh. I noticed we were missing it. Must've mixed it into the patch.
> Should I resend the patches split?
Yes, please split patch 2. That makes it easier to bisect etc. And
please note that I have already applied patch 1.
But please wait an hour or two so that I have gone through my patch
backlog. Less conflicts that way.
--
Kalle Valo
next prev parent reply other threads:[~2013-04-22 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 8:27 [ath9k-devel] [PATCH 0/2] ath10k: locking cleanup Michal Kazior
2013-04-18 8:27 ` [ath9k-devel] [PATCH 1/2] ath10k: kill vdev_mtx and use conf_mutex Michal Kazior
2013-04-22 8:08 ` Kalle Valo
2013-04-18 8:27 ` [ath9k-devel] [PATCH 2/2] ath10k: refactor scan locking Michal Kazior
2013-04-22 8:08 ` Kalle Valo
2013-04-22 8:12 ` Michal Kazior
2013-04-22 8:15 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-22 11:16 [ath9k-devel] [PATCH 0/2] ath10k: scan fixes Michal Kazior
2013-04-22 11:16 ` [ath9k-devel] [PATCH 2/2] ath10k: refactor scan locking Michal Kazior
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=87k3nvkmki.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox