Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
Cc: linux-wireless@vger.kernel.org, johannes.berg@intel.com,
	hofrat@osadl.org, xypron.glpk@gmx.de
Subject: Re: [PATCH] rsi: fix memory lean in module unload
Date: Wed, 12 Oct 2016 17:14:35 +0300	[thread overview]
Message-ID: <87shs1ejsk.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1474437546-6590-1-git-send-email-prameela.j04cs@gmail.com> (Prameela Rani Garnepudi's message of "Wed, 21 Sep 2016 11:29:06 +0530")

Prameela Rani Garnepudi <prameela.j04cs@gmail.com> writes:

> Moved debugfs entry removal under CONFIG_RSI_DEBUGFS flag
> Added freeing of below structures
>  * channels list in each supported band
>  * rsi debugfs info
>
> Signed-off-by: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>

There are four similar patches without any version information:

[  1] rsi: fix memory leak in debugfs entry and supported bands    2016-09-19 Prameela Ran Deferred
[  2] [1/1] rsi: fix memory leak in debugfs entry and supported... 2016-09-20 Prameela Ran Deferred
[  3] rsi: fix memory lean in module unload                        2016-09-21 Prameela Ran Deferred
[  4] rsi: fix memory leak in module unload                        2016-09-21 Prameela Ran Deferred

When sending a new version of the patch please add a version number to
it. See the instructions for more:

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#subject_name

-- 
Kalle Valo

      reply	other threads:[~2016-10-12 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21  5:59 [PATCH] rsi: fix memory lean in module unload Prameela Rani Garnepudi
2016-10-12 14:14 ` Kalle Valo [this message]

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=87shs1ejsk.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.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox