kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: kexec@lists.infradead.org
Subject: Re: Makedumpfile 1.4.2 release
Date: Wed, 25 Jan 2012 18:54:10 +0800	[thread overview]
Message-ID: <4F1FDF52.8050301@gmail.com> (raw)
In-Reply-To: <4F1FDE5F.5080403@gmail.com>

On 01/25/2012 06:50 PM, Cong Wang wrote:
> Hello, Kumagai-san,
>
> I saw you released 1.4.2:
>

By the way, the latest kernel supported by makedumpfile 1.4.2 is still
2.6.36.

makedumpfile.h
383:#define LATEST_VERSION		KERNEL_VERSION(2, 6, 36)/* linux-2.6.36 */

The latest stable kernel is already 3.2.1. :) So, what prevents 
makedumpfile supporting newer kernels?

Thanks.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2012-01-25 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 10:50 Makedumpfile 1.4.2 release Cong Wang
2012-01-25 10:54 ` Cong Wang [this message]
2012-01-26  5:43   ` Atsushi Kumagai
2012-01-26 10:54     ` Cong Wang
2012-01-26  1:09 ` Atsushi Kumagai
2012-01-26  3:21   ` Cong Wang

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=4F1FDF52.8050301@gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    /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;
as well as URLs for NNTP newsgroup(s).