From: Simon Horman <horms@verge.net.au>
To: Petr Tesarik <ptesarik@suse.cz>
Cc: kexec mailing list <kexec@lists.infradead.org>
Subject: Re: [v2 0/2] Fix --kexec-syscall-auto on s390x
Date: Tue, 7 Apr 2020 14:26:52 +0200 [thread overview]
Message-ID: <20200407122652.GD17530@vergenet.net> (raw)
In-Reply-To: <20200403134504.4a0304e9@ezekiel.suse.cz>
On Fri, Apr 03, 2020 at 01:45:04PM +0200, Petr Tesarik wrote:
> On Wed, 1 Apr 2020 14:40:09 +0200
> Simon Horman <horms@verge.net.au> wrote:
>
> > On Fri, Mar 13, 2020 at 03:09:27PM +0100, Petr Tesarik wrote:
> > > From: Petr Tesarik <ptesarik@suse.com>
> > >
> > > As noticed by Raymund Will, kexec -la does not work on kernels without
> > > the kexec_file_load(2) syscall, revealing some shortcomings in the
> > > automatic syscall selection.
> > >
> > > Petr Tesarik (2):
> > > kexec-tools: Fix kexec_file_load(2) error handling
> > > kexec-tools: Reset getopt before falling back to legacy syscall
> > >
> > > kexec/kexec.c | 120 ++++++++++++++++++++++++++++++++--------------------------
> >
> > Thanks, applied.
>
> Thank you very much.
>
> IBM has just found an issue with the patch, and I've already sent a
> follow-up fix. Sorry for the extra noise.
No problem, thanks for the follow-up.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2020-04-07 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200313140929.29551-1-ptesarik@suse.cz>
2020-04-01 12:40 ` [v2 0/2] Fix --kexec-syscall-auto on s390x Simon Horman
[not found] ` <20200403134504.4a0304e9@ezekiel.suse.cz>
2020-04-07 12:26 ` Simon Horman [this message]
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=20200407122652.GD17530@vergenet.net \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=ptesarik@suse.cz \
/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).