From: Kalle Valo <kvalo@codeaurora.org>
To: Prameela Rani Garnepudi <prameela.garnepudi@redpinesignals.com>
Cc: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>,
linux-wireless@vger.kernel.org, johannes.berg@intel.com,
hofrat@osadl.org, xypron.glpk@gmx.de
Subject: Re: [PATCH 1/3] rsi: Fix memory leak in module unload
Date: Wed, 26 Oct 2016 09:47:48 +0300 [thread overview]
Message-ID: <87a8dr7giz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <7a4d28a2-53ac-bc81-bf2c-452434d6768e@redpinesignals.com> (Prameela Rani Garnepudi's message of "Mon, 24 Oct 2016 11:33:40 +0530")
Prameela Rani Garnepudi <prameela.garnepudi@redpinesignals.com> writes:
> On 10/13/2016 07:56 PM, Kalle Valo wrote:
>> Kalle Valo <kvalo@codeaurora.org> writes:
>>
>>> Prameela Rani Garnepudi <prameela.j04cs@gmail.com> writes:
>>>
>>>> Observed crash when module is unloaded if CONFIG_RSI_DEBUGSFS is not set.
>>>> Fix: Debugfs entry removal moved inside CONFIG_RSI_DEBUGSFS flag in
>>>> function rsi_mac80211_detach()
>>>> Memory leak found and fixed for below structures in function
> rsi_mac80211_detach()
>>>> * channel list for each supported band
>>>> * rsi debugfs info
>>>>
>>>> Signed-off-by: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
>>> BTW, I don't see patch 2 in patchwork nor in linux-wireless, but I do
>>> see it on my inbox. Either it's slow or there was a problem with the
>>> delivery.
>> It was just slow, I see it now:
>>
>> https://patchwork.kernel.org/patch/9374987/
>>
> Hi,
> Can you please review this patch.
wireless-drivers-next is not open yet as I was on vacation last week,
hoping to open it today.
And instead of mailing me please check the status from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#checking_state_of_patches_from_patchwork
If you see lots of patches pending submitted around the same time as
yours it's a pretty good hint that I just haven't been able to go
through my queue:
https://patchwork.kernel.org/project/linux-wireless/list/?state=*&delegate=25621
--
Kalle Valo
next prev parent reply other threads:[~2016-10-26 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 11:25 [PATCH 1/3] rsi: Fix memory leak in module unload Prameela Rani Garnepudi
2016-10-13 13:11 ` Kalle Valo
2016-10-13 14:26 ` Kalle Valo
[not found] ` <7a4d28a2-53ac-bc81-bf2c-452434d6768e@redpinesignals.com>
2016-10-26 6:47 ` Kalle Valo [this message]
2016-11-17 6:44 ` [1/3] " 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=87a8dr7giz.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=hofrat@osadl.org \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=prameela.garnepudi@redpinesignals.com \
--cc=prameela.j04cs@gmail.com \
--cc=xypron.glpk@gmx.de \
/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.