From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath10k: fix unused variable warning
Date: Mon, 22 Apr 2013 11:13:49 +0300 [thread overview]
Message-ID: <87obd7kmo2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1366282788-16795-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 18 Apr 2013 12:59:48 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Thanks, applied. I just added the function name to the title.
--
Kalle Valo
next prev parent reply other threads:[~2013-04-22 8:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 10:34 [ath9k-devel] [PATCH 0/3] ath10k: pci memleak fix Michal Kazior
2013-04-17 10:34 ` [ath9k-devel] [PATCH 1/3] ath10k: drop dead code Michal Kazior
2013-04-17 10:34 ` [ath9k-devel] [PATCH 2/3] ath10k: make htc cancellation a generic thing Michal Kazior
2013-04-17 10:34 ` [ath9k-devel] [PATCH 3/3] ath10k: reorder pci shutdown sequences Michal Kazior
2013-04-17 13:12 ` [ath9k-devel] [PATCH v2 0/5] ath10k: pci memleak fix Michal Kazior
2013-04-17 13:12 ` [ath9k-devel] [PATCH v2 1/5] ath10k: drop dead code Michal Kazior
2013-04-17 13:12 ` [ath9k-devel] [PATCH v2 2/5] ath10k: make HTC cancellation a generic thing Michal Kazior
2013-04-17 13:12 ` [ath9k-devel] [PATCH v2 3/5] ath10k: fix HTC tx flushing Michal Kazior
2013-04-17 13:12 ` [ath9k-devel] [PATCH v2 4/5] ath10k: reorder pci shutdown sequences Michal Kazior
2013-04-17 13:12 ` [ath9k-devel] [PATCH v2 5/5] ath10k: fix memory leak during PCI teardown Michal Kazior
2013-04-18 10:04 ` [ath9k-devel] [PATCH v2 0/5] ath10k: pci memleak fix Kalle Valo
2013-04-18 10:29 ` Kalle Valo
2013-04-18 10:46 ` Michal Kazior
2013-04-18 10:54 ` Kalle Valo
2013-04-18 10:59 ` [ath9k-devel] [PATCH] ath10k: fix unused variable warning Michal Kazior
2013-04-22 8:13 ` Kalle Valo [this message]
2013-04-18 9:58 ` [ath9k-devel] [PATCH 0/3] ath10k: pci memleak fix 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=87obd7kmo2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.