From: Andrew Morton <akpm@linux-foundation.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
iamjoonsoo.kim@lge.com, m.szyprowski@samsung.com,
lauraa@codeaurora.org, s.strogin@partner.samsung.com
Subject: Re: [PATCH v5 1/3] mm: cma: debugfs interface
Date: Wed, 18 Feb 2015 14:18:16 -0800 [thread overview]
Message-ID: <20150218141816.08b534623efc62a778c38d27@linux-foundation.org> (raw)
In-Reply-To: <1423780008-16727-2-git-send-email-sasha.levin@oracle.com>
On Thu, 12 Feb 2015 17:26:46 -0500 Sasha Levin <sasha.levin@oracle.com> wrote:
> Implement a simple debugfs interface to expose information about CMA areas
> in the system.
I'm not seeing any description of the proposed interface in changelog,
code comments or documentation.
- What files and directories are created? Something like
/debug/cma/cma-NN, where NN represents... what?
- What are the debugfs file permissions?
- Example output along with any needed explanation?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-02-18 22:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 22:26 [PATCH v5 0/3] mm: cma: debugfs access to CMA Sasha Levin
2015-02-12 22:26 ` [PATCH v5 1/3] mm: cma: debugfs interface Sasha Levin
2015-02-13 2:48 ` Joonsoo Kim
2015-02-18 22:18 ` Andrew Morton [this message]
2015-02-12 22:26 ` [PATCH v5 2/3] mm: cma: allocation trigger Sasha Levin
2015-02-13 2:50 ` Joonsoo Kim
2015-02-19 17:38 ` Stefan Strogin
2015-02-20 10:27 ` Sasha Levin
2015-02-12 22:26 ` [PATCH v5 3/3] mm: cma: release trigger Sasha Levin
2015-02-13 2:50 ` Joonsoo Kim
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=20150218141816.08b534623efc62a778c38d27@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=s.strogin@partner.samsung.com \
--cc=sasha.levin@oracle.com \
/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