public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Bouchard Louis <louis.bouchard@canonical.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: kexec@lists.infradead.org
Subject: Re: makedumpfile availability for x86 3.2 kernels
Date: Fri, 27 Apr 2012 11:25:07 -0400	[thread overview]
Message-ID: <4F9ABA53.2060709@canonical.com> (raw)
In-Reply-To: <20120427132448.d7854fd6.kumagai-atsushi@mxc.nes.nec.co.jp>

Hello Kumagai-san,

Le 27/04/2012 00:24, Atsushi Kumagai a écrit :
> 
> Sorry, I haven't tested makedumpfile for 3.2 kernel yet, but I think it 
> will work fine. If makedumpfile doesn't work in your environmental, then
> would you report it ? 
> 
> For your information, Suzuki reported that makedumpfile works for 3.2 kernel
> on ppc32.
> 
>   http://lists.infradead.org/pipermail/kexec/2012-February/006022.html
> 
> 
> Thanks
> Atsushi Kumagai
> 

I've located where makedumpfile is being used in our build process and
I'll do my best to test it A.S.A.P.

I've also filed a bug against it, so you can follow its evolution here :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/988512

Kind regards,

...Louis

-- 
Louis Bouchard
Backline Support Analyst
Canonical Ltd
Ubuntu support: http://landscape.canonical.com

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

  reply	other threads:[~2012-04-27 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 20:27 makedumpfile availability for x86 3.2 kernels Bouchard Louis
2012-04-27  4:24 ` Atsushi Kumagai
2012-04-27 15:25   ` Bouchard Louis [this message]
2012-05-10  7:37     ` Bouchard Louis
2012-05-11  4:52       ` Atsushi Kumagai
2012-05-02 14:42   ` Bouchard Louis

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=4F9ABA53.2060709@canonical.com \
    --to=louis.bouchard@canonical.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