From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v2 0/5] ath10k: pci memleak fix
Date: Thu, 18 Apr 2013 13:54:10 +0300 [thread overview]
Message-ID: <87ppxsnm7h.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <516FCF12.4060200@tieto.com> (Michal Kazior's message of "Thu, 18 Apr 2013 12:46:42 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 18/04/13 12:29, Kalle Valo wrote:
>> Kalle Valo <kvalo@qca.qualcomm.com> writes:
>>
>>> Michal Kazior <michal.kazior@tieto.com> writes:
>>>
>>>> The v2 fixes patch 2, and introduces new patches 4
>>>> and 5. There were two possible memleaks.
>>>>
>>>> Michal Kazior (5):
>>>> ath10k: drop dead code
>>>> ath10k: make HTC cancellation a generic thing
>>>> ath10k: fix HTC tx flushing
>>>> ath10k: reorder pci shutdown sequences
>>>> ath10k: fix memory leak during PCI teardown
>>>
>>> Thanks, all five applied.
>>
>> I'm not sure, but I suspect this set added a new warning:
>>
>> drivers/net/wireless/ath/ath10k/htc.c:341:24: warning: unused variable skb_cb [-Wunused-variable]
>
> Yes. My apologies. I must've missed that somehow. It was introduced by
> patch #2.
No worries. Can you send a followup patch to fix that, please?
--
Kalle Valo
next prev parent reply other threads:[~2013-04-18 10:54 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 [this message]
2013-04-18 10:59 ` [ath9k-devel] [PATCH] ath10k: fix unused variable warning Michal Kazior
2013-04-22 8:13 ` Kalle Valo
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=87ppxsnm7h.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