From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Exporting kmemleak.h to userspace
Date: Wed, 2 Sep 2009 17:29:57 -0700 [thread overview]
Message-ID: <43e72e890909021729q7c40f907v7a81eaf5c8b73a61@mail.gmail.com> (raw)
I was reviewing kmemleak code and noticed kmemleak.h went exported to
userspace under include/linux/kmemleak.h. Do we expect userspace to
use this stuff somehow? All relevant kmemleak structs are kept
private, I'm curious what userspace apps would use this.
Luis
next reply other threads:[~2009-09-03 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 0:29 Luis R. Rodriguez [this message]
2009-09-03 6:23 ` Pekka Enberg
2009-09-03 13:18 ` Catalin Marinas
2009-09-03 13:34 ` Johannes Berg
2009-09-03 18:00 ` Luis R. Rodriguez
2009-09-03 18:04 ` Johannes Berg
2009-09-03 18:06 ` Luis R. Rodriguez
2009-09-03 18:12 ` Johannes Berg
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=43e72e890909021729q7c40f907v7a81eaf5c8b73a61@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®