From: akpm@linux-foundation.org
To: luming.yu@gmail.com, lenb@kernel.org, luming.yu@intel.com,
mm-commits@vger.kernel.org
Subject: [merged] drivers-cpufreq-acpi-cpufreqc-fix-memory-leak.patch removed from -mm tree
Date: Tue, 12 Jul 2011 13:00:48 -0700 [thread overview]
Message-ID: <201107122000.p6CK0ISA032573@imap1.linux-foundation.org> (raw)
The patch titled
drivers/cpufreq/acpi-cpufreq.c: fix memory leak
has been removed from the -mm tree. Its filename was
drivers-cpufreq-acpi-cpufreqc-fix-memory-leak.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: drivers/cpufreq/acpi-cpufreq.c: fix memory leak
From: Luming Yu <luming.yu@gmail.com>
I came across a memory leak during a cyclic cpu-online-offline test.
Signed-off-by: Yu Luming <luming.yu@intel.com>
Cc: Len Brown <lenb@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/cpufreq/acpi-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/cpufreq/acpi-cpufreq.c~drivers-cpufreq-acpi-cpufreqc-fix-memory-leak drivers/cpufreq/acpi-cpufreq.c
--- a/drivers/cpufreq/acpi-cpufreq.c~drivers-cpufreq-acpi-cpufreqc-fix-memory-leak
+++ a/drivers/cpufreq/acpi-cpufreq.c
@@ -759,7 +759,7 @@ static void __exit acpi_cpufreq_exit(voi
cpufreq_unregister_driver(&acpi_cpufreq_driver);
- free_percpu(acpi_perf_data);
+ free_acpi_perf_data();
}
module_param(acpi_pstate_strict, uint, 0644);
_
Patches currently in -mm which might be from luming.yu@gmail.com are
origin.patch
reply other threads:[~2011-07-12 20:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201107122000.p6CK0ISA032573@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=luming.yu@intel.com \
--cc=mm-commits@vger.kernel.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.