From: 21cnbao@gmail.com (Barry Song)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] MM: CMA: add a simple kernel module as the helper to test CMA
Date: Wed, 7 Mar 2012 13:40:32 +0800 [thread overview]
Message-ID: <CAGsJ_4zPn=phmWw8qSed93QWnTdOF7peh71uom0i6idR1_jFSQ@mail.gmail.com> (raw)
In-Reply-To: <4F56F0A8.1000600@gmail.com>
2012/3/7 Cong Wang <xiyou.wangcong@gmail.com>:
> On 03/07/2012 01:17 PM, Barry Song wrote:
>>
>> that is definitely trivial as we are talking about things in a test
>> module. and we are not talking about any bug in the test module as
>> well.
>
>
> I am quite sure *any* patches have bugs will not be merged, IOW, you seem
> don't want your patch merged. :) Fine. That is all.
Cong, i was not againest what you said as a techinical issue.
definitely, it can be a /proc, it is also able to be /sys if you like.
/proc is probably better than /dev from the original design thinking in kernel.
here i focused on people have this module to test CMA at runtime. i
also thought Michal also wants this module to show people the usage of
CMA as well.
i'll much appreciate if you have time to move it to /proc.
-barry
next prev parent reply other threads:[~2012-03-07 5:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 3:14 [PATCH v3] MM: CMA: add a simple kernel module as the helper to test CMA Barry Song
2012-03-07 4:14 ` Cong Wang
2012-03-07 4:49 ` Barry Song
2012-03-07 4:55 ` Cong Wang
2012-03-07 4:57 ` Barry Song
2012-03-07 5:01 ` Cong Wang
2012-03-07 5:05 ` Barry Song
2012-03-07 5:09 ` Cong Wang
2012-03-07 5:17 ` Barry Song
2012-03-07 5:22 ` Cong Wang
2012-03-07 5:40 ` Barry Song [this message]
2012-03-07 10:38 ` Barry Song
2012-03-07 10:48 ` Michal Nazarewicz
2012-03-07 10:55 ` Barry Song
2012-03-07 10:59 ` Michal Nazarewicz
2012-03-07 11:12 ` Barry Song
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='CAGsJ_4zPn=phmWw8qSed93QWnTdOF7peh71uom0i6idR1_jFSQ@mail.gmail.com' \
--to=21cnbao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).