From: "lizhengyu (E)" <lizhengyu3@huawei.com>
To: <palmer@rivosinc.com>
Cc: <alex@ghiti.fr>, <aou@eecs.berkeley.edu>, <bjorn.topel@gmail.com>,
<ebiederm@xmission.com>, <guoren@linux.alibaba.com>,
<jszhang@kernel.org>, <kexec@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<mick@ics.forth.gr>, <paul.walmsley@sifive.com>,
<penberg@kernel.org>, <sunnanyong@huawei.com>,
<wangkefeng.wang@huawei.com>, <liaochang1@huawei.com>
Subject: Re: [PATCH v3 -next 0/6] riscv: kexec: add kexec_file_load() support
Date: Thu, 19 May 2022 16:26:46 +0800 [thread overview]
Message-ID: <c07ba338-1c41-c351-c9c6-26e492a73818@huawei.com> (raw)
In-Reply-To: <20220408100914.150110-1-lizhengyu3@huawei.com>
Hi Palmer,
If it still need to be improved? Hope we can target next merge window.
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: "lizhengyu (E)" <lizhengyu3@huawei.com>
To: <palmer@rivosinc.com>
Cc: <alex@ghiti.fr>, <aou@eecs.berkeley.edu>, <bjorn.topel@gmail.com>,
<ebiederm@xmission.com>, <guoren@linux.alibaba.com>,
<jszhang@kernel.org>, <kexec@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<mick@ics.forth.gr>, <paul.walmsley@sifive.com>,
<penberg@kernel.org>, <sunnanyong@huawei.com>,
<wangkefeng.wang@huawei.com>, <liaochang1@huawei.com>
Subject: Re: [PATCH v3 -next 0/6] riscv: kexec: add kexec_file_load() support
Date: Thu, 19 May 2022 16:26:46 +0800 [thread overview]
Message-ID: <c07ba338-1c41-c351-c9c6-26e492a73818@huawei.com> (raw)
In-Reply-To: <20220408100914.150110-1-lizhengyu3@huawei.com>
Hi Palmer,
If it still need to be improved? Hope we can target next merge window.
Thanks!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: lizhengyu (E) <lizhengyu3@huawei.com>
To: kexec@lists.infradead.org
Subject: [PATCH v3 -next 0/6] riscv: kexec: add kexec_file_load() support
Date: Thu, 19 May 2022 16:26:46 +0800 [thread overview]
Message-ID: <c07ba338-1c41-c351-c9c6-26e492a73818@huawei.com> (raw)
In-Reply-To: <20220408100914.150110-1-lizhengyu3@huawei.com>
Hi Palmer,
If it still need to be improved? Hope we can target next merge window.
Thanks!
next prev parent reply other threads:[~2022-05-19 8:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 10:09 [PATCH v3 -next 0/6] riscv: kexec: add kexec_file_load() support Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` [PATCH v3 -next 1/6] kexec_file: Fix kexec_file.c build error for riscv platform Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-05-20 15:45 ` Palmer Dabbelt
2022-05-20 15:45 ` Palmer Dabbelt
2022-05-20 15:45 ` Palmer Dabbelt
2022-05-22 3:07 ` Baoquan He
2022-05-22 3:07 ` Baoquan He
2022-05-22 3:07 ` Baoquan He
2022-04-08 10:09 ` [PATCH v3 -next 2/6] RISC-V: use memcpy for kexec_file mode Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` [PATCH v3 -next 3/6] RISC-V: Add kexec_file support Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` [PATCH v3 -next 4/6] RISC-V: Support for kexec_file on panic Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` [PATCH v3 -next 5/6] RISC-V: Add purgatory Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` [PATCH v3 -next 6/6] RISC-V: Load purgatory in kexec_file Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-08 10:09 ` Li Zhengyu
2022-04-21 3:15 ` [PATCH v3 -next 0/6] riscv: kexec: add kexec_file_load() support lizhengyu (E)
2022-04-21 3:15 ` lizhengyu
2022-04-21 3:15 ` lizhengyu (E)
2022-05-19 8:26 ` lizhengyu (E) [this message]
2022-05-19 8:26 ` lizhengyu
2022-05-19 8:26 ` lizhengyu (E)
2022-05-20 15:45 ` Palmer Dabbelt
2022-05-20 15:45 ` Palmer Dabbelt
2022-05-20 15:45 ` Palmer Dabbelt
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=c07ba338-1c41-c351-c9c6-26e492a73818@huawei.com \
--to=lizhengyu3@huawei.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn.topel@gmail.com \
--cc=ebiederm@xmission.com \
--cc=guoren@linux.alibaba.com \
--cc=jszhang@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=penberg@kernel.org \
--cc=sunnanyong@huawei.com \
--cc=wangkefeng.wang@huawei.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 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.