qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <Alistair.Francis@wdc.com>
To: "sorear2@gmail.com" <sorear2@gmail.com>,
	"qemu-riscv@nongnu.org" <qemu-riscv@nongnu.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] Support separate -firmware and -kernel
Date: Mon, 17 Dec 2018 18:55:44 +0000	[thread overview]
Message-ID: <85826d60ac4fd0430d39379c3eac714d48ddf903.camel@wdc.com> (raw)
In-Reply-To: <1545001947-29444-1-git-send-email-sorear2@gmail.com>

On Sun, 2018-12-16 at 18:12 -0500, Stefan O'Rear wrote:
> This was posted in May[0] by Michael Clark.  I have split it up to
> address earlier review feedback, along with other minor cleanups.
> 
> [0]: 
> http://lists.nongnu.org/archive/html/qemu-devel/2018-05/msg05121.html

Hello Stefan,

Thanks for picking this up. I'll review your patches today.

In the future can you please ensure you CC the QEMU mailing list on any
patches submitted: qemu-devel@nongnu.org

Alistair

> 
> Stefan O'Rear (4):
>   RISC-V: Move firmware loading logic to a separate file
>   RISC-V: refactor initrd loading
>   RISC-V: Honor entry point in loaded ELF firmware
>   RISC-V: Support separate firmware and kernel payload
> 
>  hw/riscv/Makefile.objs  |   1 +
>  hw/riscv/boot.c         | 170
> ++++++++++++++++++++++++++++++++++++++++++++++++
>  hw/riscv/virt.c         |  69 ++++----------------
>  include/hw/riscv/boot.h |  24 +++++++
>  4 files changed, 208 insertions(+), 56 deletions(-)
>  create mode 100644 hw/riscv/boot.c
>  create mode 100644 include/hw/riscv/boot.h
> 

           reply	other threads:[~2018-12-17 18:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1545001947-29444-1-git-send-email-sorear2@gmail.com>]

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=85826d60ac4fd0430d39379c3eac714d48ddf903.camel@wdc.com \
    --to=alistair.francis@wdc.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sorear2@gmail.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;
as well as URLs for NNTP newsgroup(s).