From: Dave Young <dyoung@redhat.com>
To: Jingbai Ma <jingbai.ma@hp.com>
Cc: oomichi@mxs.nes.nec.co.jp, bhe@redhat.com, jin.wang@hp.com,
kexec@lists.infradead.org, gang.xing@hp.com, nan.chen2@hp.com,
lisa.mitchell@hp.com, kumagai-atsushi@mxc.nes.nec.co.jp,
nigel.croxon@hp.com, vgoyal@redhat.com
Subject: Re: [PATCH] Add a help message into man page of makedumpfile for -b option.
Date: Fri, 31 May 2013 11:22:02 +0800 [thread overview]
Message-ID: <51A8175A.6010302@redhat.com> (raw)
In-Reply-To: <51A80A66.7080003@redhat.com>
On 05/31/2013 10:26 AM, Dave Young wrote:
> Add Ken'ichi Ohmichi to cc list and remove redhat list from cc
>
> On 05/30/2013 04:44 PM, Jingbai Ma wrote:
>> This is a minor change that only adds a help message to -b option in makedumpfile man page.
>> This message has been in Red Hat's makedumpfile source, they would like it in upstream also.
>>
>> Signed-off-by: Jingbai Ma <jingbai.ma@hp.com>
>> ---
>> makedumpfile.8 | 4 ++++
>> 1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> diff --git a/makedumpfile.8 b/makedumpfile.8
>> index cfd1270..1e844db 100644
>> --- a/makedumpfile.8
>> +++ b/makedumpfile.8
>> @@ -534,6 +534,10 @@ order from left to right. \fIVMCORE\fRs are assembled into a single
>> Print debugging message.
>>
>> .TP
>> +\fB-b <order>\fR
>> +cache 2^order pages in ram when generating vmcore info before writing to output
Hi, Jingbai
A nitpick:
The first character should be capital 'C'
>> +
>> +.TP
>> \fB\-h\fR
>> Show help message and LZO/snappy support status (enabled/disabled).
>>
>>
>
>
--
Thanks
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-05-31 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 8:44 [PATCH] Add a help message into man page of makedumpfile for -b option Jingbai Ma
2013-05-31 2:26 ` Dave Young
2013-05-31 3:22 ` Dave Young [this message]
2013-06-04 7:38 ` Atsushi Kumagai
2013-06-04 10:11 ` Dave Young
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=51A8175A.6010302@redhat.com \
--to=dyoung@redhat.com \
--cc=bhe@redhat.com \
--cc=gang.xing@hp.com \
--cc=jin.wang@hp.com \
--cc=jingbai.ma@hp.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=lisa.mitchell@hp.com \
--cc=nan.chen2@hp.com \
--cc=nigel.croxon@hp.com \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=vgoyal@redhat.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