From: Simon Horman <horms@kernel.org>
To: Coiby Xu <coxu@redhat.com>
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>,
Simon Horman <horms@kernel.org>,
kexec@lists.infradead.org
Subject: Re: [ANNOUNCE] kexec-tools v2.0.27 preparation
Date: Tue, 15 Aug 2023 12:39:56 +0200 [thread overview]
Message-ID: <ZNtV/P4fPCrMevQZ@vergenet.net> (raw)
In-Reply-To: <ymdn754ihzovgpgoikjnpwueqx6zzmgcempvlr6bsn5rx3mwrw@62dmgvygv4eo>
On Mon, Aug 14, 2023 at 11:19:07AM +0800, Coiby Xu wrote:
> Hi Sourabh,
>
> On Mon, Aug 14, 2023 at 08:17:34AM +0530, Sourabh Jain wrote:
> > Hello Simon,
> >
> > Can we include below fix?
> > https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/thread/O3W4SLVVFT6J25U5YSXNZ3URZ4QY6SRU/
>
> I'll review your patch! Note the patch is against Fedora's kexec-tools
> so it doesn't apply to this upstream kexec-tools. The relationship
> between Fedora's kexec-tools and this upstream kexec-tools can be
> described as follows,
> 1. Fedora's kexec-tools packages the kexec binary which is provides by upstream
> kexec-tools; 2. The kexec binary is used for loading the kdump kernel and
> initrd but
> it's not responsible for building the kdump initrd. Fedora's kexec-tools
> is used to build the kdump initrd instead.
>
> Currrently it's WIP to split current Fedora kexec-tools into
> kexec-tools, kdump-utils, makedumpfile and eppic. Hopefully after it's
> done, you and other uses will no longer be confused by the relationship
> between Fedora's kexec-tools and this upstream kexec-tools.
Thanks for the clarification, I'm assuming no action is needed on my part
at this time. Let me know if I am mistaken.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2023-08-15 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 7:30 [ANNOUNCE] kexec-tools v2.0.27 preparation Simon Horman
2023-08-14 2:47 ` Sourabh Jain
2023-08-14 3:19 ` Coiby Xu
2023-08-14 3:50 ` Sourabh Jain
2023-08-15 10:39 ` 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=ZNtV/P4fPCrMevQZ@vergenet.net \
--to=horms@kernel.org \
--cc=coxu@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=sourabhjain@linux.ibm.com \
/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