From: Palmer Dabbelt <palmer@dabbelt.com>
To: mick@ics.forth.gr
Cc: david.abdurachmanov@sifive.com, anup@brainfault.org,
Atish Patra <Atish.Patra@wdc.com>,
yibin_liu@c-sky.com, Paul Walmsley <paul.walmsley@sifive.com>,
mick@ics.forth.gr, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 0/3] RISC-V: Add kexec/kdump support
Date: Thu, 11 Jun 2020 12:39:57 -0700 (PDT) [thread overview]
Message-ID: <mhng-3accafc5-2df8-4798-aebd-b86a0f0414b7@palmerdabbelt-glaptop1> (raw)
In-Reply-To: <f1f3932ac90089d2d07d89e05270a98d@mailhost.ics.forth.gr>
On Thu, 11 Jun 2020 12:09:08 PDT (-0700), mick@ics.forth.gr wrote:
> Στις 2020-05-21 21:42, Nick Kossifidis έγραψε:
>> Στις 2020-04-24 20:12, Nick Kossifidis έγραψε:
>>> This patch series adds kexec/kdump and crash kernel
>>> support on RISC-V. For testing the patches a patched
>>> version of kexec-tools is needed. The patch is still
>>> a work in progress but a draft version can be found at:
>>>
>>> http://riscv.ics.forth.gr/kexec-tools.patch
>>>
>>
>> Any comments / feedback on this ? Should we get it in ?
>>
>> Regards,
>> Nick
>
> Anyone ?
Sorry, I dropped the ball on this one. After the CPU hotplug breakage I
decided I need to get a pre-merge test for all these new features, and I
haven't gotten around to actually doing so yet. The merge window is closing
right now, so with any luck I'll have some time to get around to my patch
backlog -- first I need to go spin up some better testing, though.
next prev parent reply other threads:[~2020-06-11 19:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 17:12 [PATCH 0/3] RISC-V: Add kexec/kdump support Nick Kossifidis
2020-04-24 17:12 ` [PATCH 1/3] RISC-V: Add kexec support Nick Kossifidis
2020-04-24 17:12 ` [PATCH 2/3] RISC-V: Add kdump support Nick Kossifidis
2020-04-24 17:12 ` [PATCH 3/3] RISC-V: Add crash kernel support Nick Kossifidis
2020-05-21 18:42 ` [PATCH 0/3] RISC-V: Add kexec/kdump support Nick Kossifidis
2020-06-11 19:09 ` Nick Kossifidis
2020-06-11 19:39 ` Palmer Dabbelt [this message]
2020-06-13 7:24 ` Nick Kossifidis
2020-06-13 8:17 ` Anup Patel
2020-06-13 8:21 ` Nick Kossifidis
2020-06-18 23:06 ` Palmer Dabbelt
2020-06-19 8:27 ` Nick Kossifidis
2020-06-19 17:23 ` Atish Patra
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=mhng-3accafc5-2df8-4798-aebd-b86a0f0414b7@palmerdabbelt-glaptop1 \
--to=palmer@dabbelt.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=david.abdurachmanov@sifive.com \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=paul.walmsley@sifive.com \
--cc=yibin_liu@c-sky.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.