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: Tue, 30 Oct 2018 14:46:46 +0000 [thread overview]
Message-ID: <CAFEAcA_AYKP0ApmkdSXFn_pQRq3vVBbijbg7WDfTawPkvApQxw@mail.gmail.com> (raw)
In-Reply-To: <mhng-b2717513-e93b-43da-b724-f2adca348413@palmer-si-x1c4>
On 29 October 2018 at 18:41, Palmer Dabbelt <palmer@sifive.com> wrote:
> On Mon, 29 Oct 2018 10:59:47 PDT (-0700), Peter Maydell wrote:
>>
>> 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
>
>
> I think that'd be good. It makes things a bit easier on my end as I can
> ensure I don't miss any patches that end up on our list.
OK, I have set one up. The subscription page is at:
https://lists.nongnu.org/mailman/listinfo/qemu-riscv
I think I have got the list config correct but let me know if you
notice anything weird.
I suggest submitting a patch to MAINTAINERS that adds an
L: qemu-riscv@nongnu.org
line to the RISC-V section of that file.
thanks
-- PMM
next prev parent reply other threads:[~2018-10-30 14:47 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
2018-10-29 18:41 ` Palmer Dabbelt
2018-10-30 14:46 ` Peter Maydell [this message]
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_AYKP0ApmkdSXFn_pQRq3vVBbijbg7WDfTawPkvApQxw@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).