From: Dave Jones <davej@redhat.com>
To: "Steven Finney (Palm GBU)" <Steven.Finney@palm.com>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>
Subject: Re: [PATCH] Fix memory leak in cpufreq_stats.c
Date: Fri, 29 Apr 2011 15:25:56 -0400 [thread overview]
Message-ID: <20110429192555.GA8842@redhat.com> (raw)
In-Reply-To: <465E946FB313F242A955E3365C8D13A50B6403A7@ushqwmb10>
On Tue, Apr 26, 2011 at 02:39:15PM -0700, Steven Finney (Palm GBU) wrote:
> My first post here; hopefully I've done everything right.
>
> Running kmemleak on a hotplug SMP system with CONFIG_CPU_FREQ_STAT=y
> shows a cpufreq_stats related leak everytime a cpu is taken down
> (which may occur frequently on some devices). Here is a proposed
> patch which fixes the problem. Tested on ARM 2.6.35, applies cleanly to
> Linus' tree.
I can't apply this, because your mail client sent it in a form
that isn't plaintext. Git doesn't eat base64, or winmail.dat.
Dave
prev parent reply other threads:[~2011-04-29 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:39 [PATCH] Fix memory leak in cpufreq_stats.c Steven Finney (Palm GBU)
2011-04-29 19:25 ` Dave Jones [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=20110429192555.GA8842@redhat.com \
--to=davej@redhat.com \
--cc=Steven.Finney@palm.com \
--cc=cpufreq@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox