From: lijiang <lijiang@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: bhe@redhat.com, corbet@lwn.net, kexec@lists.infradead.org,
linux-doc@vger.kernel.org, vgoyal@redhat.com
Subject: Re: [PATCH] docs: admin-guide: update kdump documentation due to change of crash URL
Date: Wed, 23 Sep 2020 10:09:39 +0800 [thread overview]
Message-ID: <e07a5f8a-0f9c-c1c3-61fc-3fc0602e6e37@redhat.com> (raw)
In-Reply-To: <20200918080958.19841-1-lijiang@redhat.com>
在 2020年09月18日 16:09, Lianbo Jiang 写道:
> Since crash utility has moved to github, the original URL is no longer
^
has been moved to github
Because of the above mistake, I'd like to correct it and reply it with the v2.
Thanks.
> available. Let's update it accordingly.
>
> Suggested-by: Dave Young <dyoung@redhat.com>
> Signed-off-by: Lianbo Jiang <lijiang@redhat.com>
> ---
> Documentation/admin-guide/kdump/kdump.rst | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/kdump/kdump.rst b/Documentation/admin-guide/kdump/kdump.rst
> index 2da65fef2a1c..75a9dd98e76e 100644
> --- a/Documentation/admin-guide/kdump/kdump.rst
> +++ b/Documentation/admin-guide/kdump/kdump.rst
> @@ -509,9 +509,12 @@ ELF32-format headers using the --elf32-core-headers kernel option on the
> dump kernel.
>
> You can also use the Crash utility to analyze dump files in Kdump
> -format. Crash is available on Dave Anderson's site at the following URL:
> +format. Crash is available at the following URL:
>
> - http://people.redhat.com/~anderson/
> + https://github.com/crash-utility/crash
> +
> +Crash document can be found at:
> + https://crash-utility.github.io/
>
> Trigger Kdump on WARN()
> =======================
>
next prev parent reply other threads:[~2020-09-23 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 8:09 Lianbo Jiang
2020-09-23 2:09 ` lijiang [this message]
2020-09-24 1:56 ` [PATCH v2] " lijiang
2020-09-24 16:43 ` Jonathan Corbet
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=e07a5f8a-0f9c-c1c3-61fc-3fc0602e6e37@redhat.com \
--to=lijiang@redhat.com \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®