From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: YOSHIDA Masanori <masanori.yoshida.tv@hitachi.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@mit.edu>,
Borislav Petkov <borislav.petkov@amd.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Kevin Hilman <khilman@ti.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Michal Marek <mmarek@suse.cz>, Rik van Riel <riel@redhat.com>,
Tejun Heo <tj@kernel.org>, Yinghai Lu <yinghai@kernel.org>,
frank.rowand@am.sony.com, jan.kiszka@web.de,
yrl.pp-manager.tt@hitachi.com
Subject: Re: [RFC PATCH 2/5] livedump: Add the new misc device "livedump"
Date: Tue, 20 Dec 2011 10:48:26 -0500 [thread overview]
Message-ID: <4EF0AE4A.3090509@gmail.com> (raw)
In-Reply-To: <20111220072343.GC9220@t3500.sdl.hitachi.co.jp>
(12/20/11 2:23 AM), YOSHIDA Masanori wrote:
> Introduces the new misc device "livedump".
> The device only has open, close and empty ioctl operations.
When cc me, please cc whole patches. Now I don't find patch [0/5] yet.
so I haven't understand what problem do you tried to solve.
Moreover, mere 2 lines patch description is not good idea if you want
to add new device and/or new feature. Please imagine 'git log' only file
this 2 lines.
next prev parent reply other threads:[~2011-12-20 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111220072028.9113.74876.stgit@t3500.sdl.hitachi.co.jp>
2011-12-20 7:23 ` YOSHIDA Masanori
2011-12-20 15:48 ` KOSAKI Motohiro [this message]
2011-12-20 7:23 ` [RFC PATCH 3/5] livedump: Add page splitting functionality YOSHIDA Masanori
2011-12-20 7:24 ` [RFC PATCH 4/5] livedump: Add write protection management YOSHIDA Masanori
2011-12-20 7:24 ` [RFC PATCH 5/5] livedump: Add memory dumping functionality YOSHIDA Masanori
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=4EF0AE4A.3090509@gmail.com \
--to=kosaki.motohiro@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=borislav.petkov@amd.com \
--cc=frank.rowand@am.sony.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@web.de \
--cc=khilman@ti.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=masanori.yoshida.tv@hitachi.com \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=mtosatti@redhat.com \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
--cc=yrl.pp-manager.tt@hitachi.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
Powered by JetHome