From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 16489] kmemleak after suspend2ram in cpufreq driver
Date: Sun, 3 Oct 2010 20:21:56 GMT [thread overview]
Message-ID: <201010032021.o93KLuww001593@demeter2.kernel.org> (raw)
In-Reply-To: <bug-16489-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16489
Toralf Förster <toralf.foerster@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
--- Comment #2 from Toralf Förster <toralf.foerster@gmx.de> 2010-10-03 20:21:54 ---
*** This bug has been marked as a duplicate of bug 15807 ***
--
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:[~2010-10-03 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 14:19 [Bug 16489] New: kmemleak after suspend2ram in cpufreq driver bugzilla-daemon
2010-08-23 12:51 ` [Bug 16489] " bugzilla-daemon
2010-09-23 21:30 ` bugzilla-daemon
2010-09-23 21:30 ` bugzilla-daemon
2010-09-28 20:30 ` bugzilla-daemon
2010-10-03 20:21 ` bugzilla-daemon [this message]
2011-03-03 1:11 ` 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=201010032021.o93KLuww001593@demeter2.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