From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 1/5] ath10k: replace debug_mtx with conf_mutex
Date: Thu, 18 Apr 2013 12:44:59 +0300 [thread overview]
Message-ID: <87ip3kqijo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1366178645-13983-2-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Wed, 17 Apr 2013 08:04:01 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> It's not a good to have too many mutexes. The
> patch simplifies locking of debufs to use
> conf_mutex.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
[...]
> @@ -328,7 +328,7 @@ int ath10k_debug_create(struct ath10k *ar)
> return -ENOMEM;
>
> init_completion(&ar->debug.event_stats_compl);
> - mutex_init(&ar->debug.debug_mtx);
> + mutex_init(&ar->conf_mutex);
Can this be right? We already initialise conf_mutex in core.c.
--
Kalle Valo
next prev parent reply other threads:[~2013-04-18 9:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 6:04 [ath9k-devel] [PATCH 0/5] ath10k: cleanups Michal Kazior
2013-04-17 6:04 ` [ath9k-devel] [PATCH 1/5] ath10k: replace debug_mtx with conf_mutex Michal Kazior
2013-04-18 9:44 ` Kalle Valo [this message]
2013-04-18 9:48 ` Michal Kazior
2013-04-17 6:04 ` [ath9k-devel] [PATCH 2/5] ath10k: change wmi structure access Michal Kazior
2013-04-17 6:04 ` [ath9k-devel] [PATCH 3/5] ath10k: fix coding style Michal Kazior
2013-04-17 6:04 ` [ath9k-devel] [PATCH 4/5] ath10k: use ath10k_warn() instead of ath10k_info() Michal Kazior
2013-04-17 6:04 ` [ath9k-devel] [PATCH 5/5] ath10k: fix function prototype argument name Michal Kazior
2013-04-18 9:50 ` [ath9k-devel] [PATCH 0/5] ath10k: cleanups Kalle Valo
2013-04-18 10:01 ` [ath9k-devel] [PATCH v2 " Michal Kazior
2013-04-18 10:01 ` [ath9k-devel] [PATCH v2 1/5] ath10k: replace debug_mtx with conf_mutex Michal Kazior
2013-04-18 10:01 ` [ath9k-devel] [PATCH v2 2/5] ath10k: change wmi structure access Michal Kazior
2013-04-18 10:01 ` [ath9k-devel] [PATCH v2 3/5] ath10k: fix coding style Michal Kazior
2013-04-18 10:01 ` [ath9k-devel] [PATCH v2 4/5] ath10k: use ath10k_warn() instead of ath10k_info() Michal Kazior
2013-04-18 10:01 ` [ath9k-devel] [PATCH v2 5/5] ath10k: fix function prototype argument name Michal Kazior
2013-04-22 8:10 ` [ath9k-devel] [PATCH v2 0/5] ath10k: cleanups Kalle Valo
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=87ip3kqijo.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