From: Simon Horman <horms@kernel.org>
To: Julian Winkler <julian.winkler1@web.de>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] x86: add devicetree support
Date: Mon, 20 Feb 2023 16:01:45 +0100 [thread overview]
Message-ID: <Y/OLWRZ4nHiNimgL@vergenet.net> (raw)
In-Reply-To: <20230219101813.903377-1-julian.winkler1@web.de>
On Sun, Feb 19, 2023 at 11:18:13AM +0100, Julian Winkler wrote:
> Since linux kernel has dropped support for simple firmware interface
> (SFI), the only way of boot newer versions on intel MID platform is
> using devicetree
Thanks Julian,
in general this patch looks fine to me.
Could I ask you to post a v2 that:
1. Is rebased on main - there was some fuzz in kexec-bzImage.c when
applying this patch locally.
2. Include a Signed-off-by line.
See "Sign your work - the Developer’s Certificate of Origin" in
https://www.kernel.org/doc/html/v6.2/process/submitting-patches.html
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2023-02-20 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 10:18 [PATCH] x86: add devicetree support Julian Winkler
2023-02-20 15:01 ` 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=Y/OLWRZ4nHiNimgL@vergenet.net \
--to=horms@kernel.org \
--cc=julian.winkler1@web.de \
--cc=kexec@lists.infradead.org \
/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