All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Cc: hbabu@us.ibm.com, rob@landley.net,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/kdump: Remove TODO in this document
Date: Thu, 23 May 2013 10:35:55 -0400	[thread overview]
Message-ID: <20130523143555.GI2779@redhat.com> (raw)
In-Reply-To: <519DD397.6060301@cn.fujitsu.com>

On Thu, May 23, 2013 at 04:30:15PM +0800, Zhang Yanfei wrote:
> We have already had the relocatable kernel, so just remove
> the TODO in the kdump document.
> 
> Signed-off-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>

Acked-by: Vivek Goyal <vgoyal@redhat.com>

Vivek

> ---
>  Documentation/kdump/kdump.txt |    8 --------
>  1 files changed, 0 insertions(+), 8 deletions(-)
> 
> diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
> index 9c7fd98..a8b291d 100644
> --- a/Documentation/kdump/kdump.txt
> +++ b/Documentation/kdump/kdump.txt
> @@ -461,14 +461,6 @@ format. Crash is available on Dave Anderson's site at the following URL:
>     http://people.redhat.com/~anderson/
>  
>  
> -To Do
> -=====
> -
> -1) Provide relocatable kernels for all architectures to help in maintaining
> -   multiple kernels for crash_dump, and the same kernel as the system kernel
> -   can be used to capture the dump.
> -
> -
>  Contact
>  =======
>  
> -- 
> 1.7.1

  reply	other threads:[~2013-05-23 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  8:30 [PATCH] Documentation/kdump: Remove TODO in this document Zhang Yanfei
2013-05-23 14:35 ` Vivek Goyal [this message]
2013-05-24  4:54 ` Rob Landley
2013-05-24  5:25   ` Zhang Yanfei

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=20130523143555.GI2779@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hbabu@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=zhangyanfei@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.