From: Jonathan Corbet <corbet@lwn.net>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, kexec@lists.infradead.org,
akpm@linux-foundation.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Hari Bathini <hbathini@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Russell King <linux@armlinux.org.uk>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"H. Peter Anvin" <hpa@zytor.com>,
vgoyal@redhat.com, x86@kernel.org,
Eric Biederman <ebiederm@xmission.com>,
dyoung@redhat.com
Subject: Re: [PATCH v3] Documentation: kdump: update kdump guide
Date: Sun, 13 Jun 2021 17:44:42 -0600 [thread overview]
Message-ID: <87sg1l9vo5.fsf@meer.lwn.net> (raw)
In-Reply-To: <878s3dbbuz.fsf@meer.lwn.net>
Jonathan Corbet <corbet@lwn.net> writes:
> Baoquan He <bhe@redhat.com> writes:
>
>> Some parts of the guide are aged, hence need be updated.
>>
>> 1) The backup area of the 1st 640K on X86_64 has been removed
>> by below commits, update the description accordingly.
>>
>> commit 7c321eb2b843 ("x86/kdump: Remove the backup region handling")
>> commit 6f599d84231f ("x86/kdump: Always reserve the low 1M when the crashkernel option is specified")
>>
>> 2) Sort out the descripiton of "crashkernel syntax" part.
>>
>> 3) And some other minor cleanups.
>>
>> Signed-off-by: Baoquan He <bhe@redhat.com>
>
> Applied, thanks.
Actually, this patch added a docs build warning:
/stuff/k/git/kernel/Documentation/admin-guide/kdump/kdump.rst:286: WARNING: Literal block ends without a blank line; unexpected unindent.
I've gone ahead and inserted the blank line to fix this. In the future,
please build-test your changes to make sure that you are not adding new
warnings.
Thanks,
jon
next prev parent reply other threads:[~2021-06-13 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 8:32 [PATCH v3] Documentation: kdump: update kdump guide Baoquan He
2021-06-09 12:20 ` Dave Young
2021-06-13 23:09 ` Jonathan Corbet
2021-06-13 23:44 ` Jonathan Corbet [this message]
2021-06-15 1:08 ` Baoquan He
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=87sg1l9vo5.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gor@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mpe@ellerman.id.au \
--cc=tsbogend@alpha.franken.de \
--cc=vgoyal@redhat.com \
--cc=will@kernel.org \
--cc=x86@kernel.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