From: Simon Horman <horms@kernel.org>
To: Brian Mak <makb@juniper.net>
Cc: kexec@lists.infradead.org, Baoquan He <bhe@redhat.com>,
Alexander Graf <graf@amazon.com>
Subject: Re: [PATCH 0/3] kexec-tools: Add new KEXEC_FILE flags
Date: Mon, 20 Jul 2026 10:40:46 +0100 [thread overview]
Message-ID: <20260720094046.GE1736709@horms.kernel.org> (raw)
In-Reply-To: <20260612223945.1400554-1-makb@juniper.net>
On Fri, Jun 12, 2026 at 03:39:42PM -0700, Brian Mak wrote:
> Hi all,
>
> I realized I forgot to raise a patch series for adding the new kexec_file flags.
> Apologies for the delay on this.
>
> This series adds support for the KEXEC_FILE_NO_CMA and KEXEC_FILE_FORCE_DTB
> flags, which are used by the --no-cma and --force-dtb options respectively.
>
> I also saw that there's no debug print for the flags passed to kexec_file_load,
> so I added a print for that as well, which was useful for me to verify these
> patches.
>
> Please let me know if there's any questions or comments.
Thanks, and likewise sorry for the delay.
Applied as:
- kexec: Add kexec_file_load debug print
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=29898e149feb
- kexec: Add DTB carryover support on x86
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=d5a495bfbfc9
- kexec: Add support for disabling usage of CMA
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=e4de788721cb
prev parent reply other threads:[~2026-07-20 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 22:39 [PATCH 0/3] kexec-tools: Add new KEXEC_FILE flags Brian Mak
2026-06-12 22:39 ` [PATCH 1/3] kexec: Add support for disabling usage of CMA Brian Mak
2026-06-12 22:39 ` [PATCH 2/3] kexec: Add DTB carryover support on x86 Brian Mak
2026-06-12 22:39 ` [PATCH 3/3] kexec: Add kexec_file_load debug print Brian Mak
2026-07-20 9:40 ` 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=20260720094046.GE1736709@horms.kernel.org \
--to=horms@kernel.org \
--cc=bhe@redhat.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=makb@juniper.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.