From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Vegard Nossum <vegard.nossum@gmail.com>, Ingo Molnar <mingo@elte.hu>
Cc: Vegard Nossum <vegardno@ifi.uio.no>,
Dave Airlie <airlied@redhat.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: fix leak of uninitialized data to userspace (acpi_system_read_event)
Date: Sat, 11 Oct 2008 00:55:05 -0700 (PDT) [thread overview]
Message-ID: <974167.43188.qm@web38207.mail.mud.yahoo.com> (raw)
> From: Vegard Nossum <vegard.nossum@gmail.com>
>
> Does that also mean that the DRM patch fixed the first one? :-)
Yes, that's "the original kmemcheck drm warning is no longer present with your patch".
Tested-by: Sitsofe Wheeler <sitsofe@yahoo.com>
next reply other threads:[~2008-10-11 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 7:55 Sitsofe Wheeler [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-10 13:26 [PATCH] drm: fix leak of uninitialized data to userspace (acpi_system_read_event) Sitsofe Wheeler
2008-10-10 14:37 ` Ingo Molnar
2008-10-10 15:26 ` Vegard Nossum
2008-10-10 15:32 ` Ingo Molnar
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=974167.43188.qm@web38207.mail.mud.yahoo.com \
--to=sitsofe@yahoo.com \
--cc=airlied@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.com \
--cc=vegardno@ifi.uio.no \
/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