From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 23712] kmemleak in cpufreq_register_driver
Date: Wed, 16 Mar 2011 20:40:13 GMT [thread overview]
Message-ID: <201103162040.p2GKeDin009730@demeter1.kernel.org> (raw)
In-Reply-To: <bug-23712-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=23712
Toralf Förster <toralf.foerster@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |CODE_FIX
--- Comment #2 from Toralf Förster <toralf.foerster@gmx.de> 2011-03-16 20:40:12 ---
solved in 2.6.38
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-03-16 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 8:48 [Bug 23712] New: kmemleak in cpufreq_register_driver bugzilla-daemon
2010-12-16 15:04 ` [Bug 23712] " bugzilla-daemon
2011-03-16 20:40 ` bugzilla-daemon [this message]
2011-07-30 6:26 ` bugzilla-daemon
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=201103162040.p2GKeDin009730@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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