All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Michael Clark <mjc@sifive.com>
Cc: "Richard W.M. Jones" <rjones@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	RISC-V Patches <patches@groups.riscv.org>
Subject: Re: [Qemu-devel] [PULL 0/1] RISC-V: Critical fixes for QEMU 2.12
Date: Tue, 3 Apr 2018 15:50:39 +0100	[thread overview]
Message-ID: <CAFEAcA-RUFi5U1rc+K=jBSCXTz1KYaECJN0Vz+POh1pFr-mjXQ@mail.gmail.com> (raw)
In-Reply-To: <CAHNT7Nt4v1R27paaETG1=vjftL8+OjoWntiRSDB1Hn1DEyHNPg@mail.gmail.com>

On 3 April 2018 at 03:43, Michael Clark <mjc@sifive.com> wrote:
> I submitted the pull request for your's/Stefan's workaround so that QEMU
> 2.12 has working FP context switching under Linux (always returning dirty or
> off is valid implementation choice according to the specification), given
> Richard Henderson had not made a PR for his more comprehensive fix, with the
> rationale that we could implement the comprehensive fix for QEMU 2.13

Given that riscv is your area as submaintainer I (and likely also
RTH) would expect RTH's patch to go in via a pull request from you,
not one directly from him. One of the things the submaintainer does
is evaluate what the right set of patches to go in for the area are,
if there are multiple proposed ways to fix something.

thanks
-- PMM

  reply	other threads:[~2018-04-03 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29 17:26 [Qemu-devel] [PULL 0/1] RISC-V: Critical fixes for QEMU 2.12 Michael Clark
2018-03-29 17:26 ` [Qemu-devel] [PULL 1/1] RISC-V: Workaround for critical mstatus.FS bug Michael Clark
2018-03-30 17:08 ` [Qemu-devel] [PULL 0/1] RISC-V: Critical fixes for QEMU 2.12 Michael Clark
2018-04-01 18:49   ` Richard W.M. Jones
2018-04-03  2:43     ` Michael Clark
2018-04-03 14:50       ` Peter Maydell [this message]
2018-03-31  6:35 ` no-reply
2018-04-03 14:58 ` Peter Maydell

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='CAFEAcA-RUFi5U1rc+K=jBSCXTz1KYaECJN0Vz+POh1pFr-mjXQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=mjc@sifive.com \
    --cc=patches@groups.riscv.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=rjones@redhat.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.