qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: "Alistair Francis" <alistair23@gmail.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>,
	"Michael Clark" <mjc@sifive.com>,
	"Alistair Francis" <Alistair.Francis@wdc.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Sagar Karandikar" <sagark@eecs.berkeley.edu>
Subject: Re: [Qemu-devel] [PATCH] Add Alistair as a RISC-V Maintainer
Date: Mon, 29 Oct 2018 17:59:47 +0000	[thread overview]
Message-ID: <CAFEAcA_oMG2qo_W_OFfdkPomu7-hc4vkFSZnC0CLQ_PD6zmW+Q@mail.gmail.com> (raw)
In-Reply-To: <mhng-81205b33-ccd0-4600-9fbd-0a025c55dcfa@palmer-si-x1c4>

On 29 October 2018 at 17:14, Palmer Dabbelt <palmer@sifive.com> wrote:
> I don't think we have anything ready to go right now: your PCIe patches
> still have some outstanding feedback (on interrupt stuff), and Bastian's
> decodetree stuff has some patches from Richard Henderson that should be
> merged in.  I was hoping to get through reviewing Michael's patches to fix
> the FS dirty bit, but haven't had time yet -- they're tested, but I haven't
> actually read through them.
>
> Maybe we should get a RISC-V QEMU mailing list so we can keep everyone in
> sync without spamming the whole world?

We can sort out a qemu-riscv mailing list like the ones we have
for ppc and arm if you like:
https://wiki.qemu.org/Contribute/MailingLists

Our general principle is that all posts should cc qemu-devel as
well as the subsystem list; the idea is that if you only care
about riscv you can just subscribe to the lower volume list, but
people on qemu-devel still get to see everything without having
to subscribe to half a dozen different other lists.

NB: softfreeze is tomorrow, which is our deadline by which any
pull requests for new feature work should be on the mailing list.
After that it's bugfixes only. So my feeling is that both the
decodetree and the PCI patches have missed the boat for 3.1
and can be dealt with in a more leisurely timescale.

If you have bugfixes in your tree that could do with being
upstreamed, this is a good time in the release cycle to look
at doing that, I think.

thanks
-- PMM

  parent reply	other threads:[~2018-10-29 18:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 16:16 [Qemu-devel] [PATCH] Add Alistair as a RISC-V Maintainer Palmer Dabbelt
2018-10-29 16:30 ` Philippe Mathieu-Daudé
2018-10-29 16:48   ` Alistair Francis
2018-10-29 17:14     ` Palmer Dabbelt
2018-10-29 17:24       ` Alistair Francis
2018-10-29 17:59       ` Peter Maydell [this message]
2018-10-29 18:41         ` Palmer Dabbelt
2018-10-30 14:46           ` Peter Maydell
2018-10-30 17:54             ` Philippe Mathieu-Daudé
2018-10-30 17:56               ` Peter Maydell
2018-10-30 18:54                 ` Peter Maydell
2018-10-29 17:07   ` 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=CAFEAcA_oMG2qo_W_OFfdkPomu7-hc4vkFSZnC0CLQ_PD6zmW+Q@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=Alistair.Francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=mjc@sifive.com \
    --cc=palmer@sifive.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sagark@eecs.berkeley.edu \
    /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).