Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Kossifidis <mick@ics.forth.gr>
To: palmer@dabbelt.com, linux-riscv@lists.infradead.org
Cc: david.abdurachmanov@sifive.com, anup@brainfault.org,
	atish.patra@wdc.com, yibin_liu@c-sky.com,
	paul.walmsley@sifive.com, mick@ics.forth.gr
Subject: Re: [PATCH 0/3] RISC-V: Add kexec/kdump support
Date: Thu, 21 May 2020 21:42:58 +0300	[thread overview]
Message-ID: <ac64bfe1ea375e583a12e396c48e1d97@mailhost.ics.forth.gr> (raw)
In-Reply-To: <20200424171214.1515457-1-mick@ics.forth.gr>

Στις 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


  parent reply	other threads:[~2020-05-21 18:43 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 ` Nick Kossifidis [this message]
2020-06-11 19:09   ` [PATCH 0/3] RISC-V: Add kexec/kdump support Nick Kossifidis
2020-06-11 19:39     ` Palmer Dabbelt
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=ac64bfe1ea375e583a12e396c48e1d97@mailhost.ics.forth.gr \
    --to=mick@ics.forth.gr \
    --cc=anup@brainfault.org \
    --cc=atish.patra@wdc.com \
    --cc=david.abdurachmanov@sifive.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox