From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>, kexec@lists.infradead.org
Subject: Re: [PATCH v2 0/3] kexec support for Linux/m68k (tools part)
Date: Tue, 5 Nov 2013 16:05:13 +0900 [thread overview]
Message-ID: <20131105070513.GB16448@verge.net.au> (raw)
In-Reply-To: <CAMuHMdVsKLBt8MiZ-dpX7expx+37XfO2kUjbRA_h5eMcsWJ1VQ@mail.gmail.com>
On Sun, Nov 03, 2013 at 03:08:50PM +0100, Geert Uytterhoeven wrote:
> On Wed, Oct 16, 2013 at 9:22 AM, Simon Horman <horms@verge.net.au> wrote:
> > I've taken a quick look over this and it seems reasonable to me.
>
> Thanks!
>
> > However, I wonder if I should wait for review of the kernel-side
> > to be completed before applying the kexec-tools patches.
> >
> > Let me know what you think.
>
> The kexec-tools part seems to be stable. The issues to be sorted out are on
> the kernel side.
>
> However, it doesn't hurt to wait a little bit more to apply this. We m68k
> people are patient and used to multi-year development ;-)
It is said that patience is a virtue :^)
As the kexec-tools portion of this change isn't useful without the
kernel portion I think I would like to wait before applying this series.
Please repost once the kernel changes have been merged or if you
would like them re-considered for any other reason.
next prev parent reply other threads:[~2013-11-05 7:05 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 [this message]
2013-12-01 11:40 ` Geert Uytterhoeven
2013-12-13 0:51 ` Simon Horman
2013-12-13 0:53 ` Simon Horman
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=20131105070513.GB16448@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