Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Pingfan Liu <piliu@redhat.com>
Cc: Eric Biederman <ebiederm@xmission.com>,
	Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Jan Hendrik Farr <kernel@jfarr.cc>,
	Philipp Rudo <prudo@redhat.com>,
	Lennart Poettering <mzxreary@0pointer.de>,
	kexec@lists.infradead.org
Subject: Re: [PATCH 2/3] kexec: Introduce UKI image parser
Date: Tue, 15 Oct 2024 14:26:10 +0100	[thread overview]
Message-ID: <20241015132610.GA2162@kernel.org> (raw)
In-Reply-To: <CAF+s44QRNpBrRuJsuVwvZduHTLhEFTtUz3fU5=4YNAn8sbBccw@mail.gmail.com>

On Mon, Oct 14, 2024 at 10:43:34AM +0800, Pingfan Liu wrote:
> Hello everyone,
> 
> I have created V2 and make a PR: https://github.com/horms/kexec-tools/pull/9
> 
> Due to utilizing the workflow in github to have some basic checks
> automatically , I migrated it to github instead of mailing-list.
> 
> Please share your opinions.

I appreciate you making use of GitHub,
but please post patch submissions using the email workflow.

Thanks!

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2024-10-15 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 11:54 [PATCH 0/3] kexec: Add support for UKI format kernel Pingfan Liu
2024-10-08 11:54 ` [PATCH 1/3] kexec: Introduce default_initrd_fd to pass internal initrd information Pingfan Liu
2024-10-08 11:54 ` [PATCH 2/3] kexec: Introduce UKI image parser Pingfan Liu
2024-10-11  8:44   ` Simon Horman
2024-10-11 11:14     ` Pingfan Liu
2024-10-14  2:43       ` Pingfan Liu
2024-10-15 13:26         ` Simon Horman [this message]
2024-10-16 11:37           ` Pingfan Liu
2024-10-08 11:54 ` [PATCH 3/3] arm64: Support UKI image format Pingfan Liu

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=20241015132610.GA2162@kernel.org \
    --to=horms@kernel.org \
    --cc=ardb@kernel.org \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=kernel@jfarr.cc \
    --cc=kexec@lists.infradead.org \
    --cc=mzxreary@0pointer.de \
    --cc=piliu@redhat.com \
    --cc=prudo@redhat.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