From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Dave Young <dyoung@redhat.com>
Cc: linux-efi <linux-efi@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Takashi Iwai <tiwai@suse.de>,
kexec@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Arvind Sankar <nivedita@alum.mit.edu>, Gary Lin <glin@suse.com>,
Sergey Shatunov <me@prok.pw>,
Colin Ian King <colin.king@canonical.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@suse.de>, Jiri Slaby <jslaby@suse.cz>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [GIT PULL 0/9] EFI fixes for v5.7-rc
Date: Sat, 11 Apr 2020 15:43:51 -0400 [thread overview]
Message-ID: <20200411194351.GQ45598@mit.edu> (raw)
In-Reply-To: <20200410135442.GA6772@dhcp-128-65.nay.redhat.com>
On Fri, Apr 10, 2020 at 09:54:42PM +0800, Dave Young wrote:
>
> The runtime cleanup looks a very good one, but I also missed that,
> userspace kexec-tools will break with the efi setup_data changes. But
> kexec_file_load will just work with the cleanup applied.
Hmmm, I wonder if there could be some kselftest or kunit tests that
would make it easier to pick up these sorts of regressions earlier?
- Ted
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2020-04-11 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200409130434.6736-1-ardb@kernel.org>
[not found] ` <20200409190109.GB45598@mit.edu>
[not found] ` <CAMj1kXGiA3PAybR7r9tatL7WV5iU7B1OQxQok3d-JmRnhX1TnA@mail.gmail.com>
[not found] ` <20200409201632.GC45598@mit.edu>
[not found] ` <CAMj1kXFqKGSqm_y+ht4mmmu10TrhSyiTG8V3PxRYGodpZ=xNFQ@mail.gmail.com>
[not found] ` <20200409235716.GF45598@mit.edu>
[not found] ` <CAMj1kXH4VtNcJugpG_UR10ewGiOApTiw=C3FsuyAQQyg67Q8Aw@mail.gmail.com>
2020-04-10 13:54 ` [GIT PULL 0/9] EFI fixes for v5.7-rc Dave Young
2020-04-11 19:43 ` Theodore Y. Ts'o [this message]
2020-04-12 3:51 ` Dave Young
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=20200411194351.GQ45598@mit.edu \
--to=tytso@mit.edu \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@suse.de \
--cc=colin.king@canonical.com \
--cc=dyoung@redhat.com \
--cc=glin@suse.com \
--cc=jslaby@suse.cz \
--cc=kexec@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@prok.pw \
--cc=mingo@kernel.org \
--cc=nivedita@alum.mit.edu \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
/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