public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, kexec@lists.infradead.org
Subject: Re: [PATCH v2 0/3] kexec support for Linux/m68k (tools part)
Date: Fri, 13 Dec 2013 09:53:22 +0900	[thread overview]
Message-ID: <20131213005322.GJ32101@verge.net.au> (raw)
In-Reply-To: <1381859460-13645-1-git-send-email-geert@linux-m68k.org>

On Tue, Oct 15, 2013 at 07:50:57PM +0200, Geert Uytterhoeven wrote:
> kexec support for Linux/m68k (tools part)
> 
> This is a set of patches to add kexec support for m68k to kexec-tools.
> 
>   - Kexec only, no kdump support yet (do you have enough RAM to keep a
>     crashdump kernel in memory at all times? ;-)

Thanks, applied.

  parent reply	other threads:[~2013-12-13  0:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 17:50 [PATCH v2 0/3] kexec support for Linux/m68k (tools part) Geert Uytterhoeven
2013-10-15 17:50 ` [PATCH 1/3] kexec: Let slurp_file_len() return the number of bytes read Geert Uytterhoeven
2013-10-15 17:50 ` [PATCH 2/3] kexec: Extract slurp_fd() Geert Uytterhoeven
2013-10-15 17:51 ` [PATCH 3/3] kexec: Add m68k support Geert Uytterhoeven
2014-09-22 20:04   ` [PATCH] kexec: distribute kexec/arch/m68k/bootinfo.h Andreas Schwab
2014-10-12 19:37   ` Andreas Schwab
2014-10-14  5:06     ` Simon Horman
2013-10-16  7:22 ` [PATCH v2 0/3] kexec support for Linux/m68k (tools part) Simon Horman
2013-11-03 14:08   ` Geert Uytterhoeven
2013-11-05  7:05     ` Simon Horman
2013-12-01 11:40       ` Geert Uytterhoeven
2013-12-13  0:51         ` Simon Horman
2013-12-13  0:53 ` Simon Horman [this message]
2013-12-13  8:03   ` Geert Uytterhoeven
2013-12-14  0:31     ` Simon Horman

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=20131213005322.GJ32101@verge.net.au \
    --to=horms@verge.net.au \
    --cc=geert@linux-m68k.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-m68k@lists.linux-m68k.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