qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v1 0/5] Misc RISC-V patches


From: Palmer Dabbelt
Subject: Re: [Qemu-devel] [PATCH v1 0/5] Misc RISC-V patches
Date: Tue, 16 Oct 2018 11:35:56 -0700 (PDT)

On Tue, 16 Oct 2018 01:05:11 PDT (-0700), address@hidden wrote:
On 15 October 2018 at 21:28, Palmer Dabbelt <address@hidden> wrote:
On Fri, 12 Oct 2018 02:34:12 PDT (-0700), address@hidden wrote:
The expected patch flow for QEMU is:
 * original patch author posts patch to qemu-devel
   (this applies also if the author happens to be the
   submaintainer)
 * patch gets reviewed on this mailing list, by you or
   anybody else
 * patches relevant to risc-v get collected up by the
   submaintainer
 * submaintainer submits those patches via pull request
   (with a frequency usually about every two weeks, more
   often if volume of patches merits it)


This makes sense.  It's almost exactly the Linux flow, which I'm used to and
I have down to a fairly mechanical process.  I think the real issue here is
that we don't have anyone who has officially committed to doing this, so I'm
just going to pull the trigger and say I'm doing so.

Thanks for picking this up.

My Linux PR flow is to tag a PR on Mondays, send it out to the list for
comments, and then if it passes muster to submit an official PR on
Wednesdays.  It's been working smoothly (we've yet to have to kill a PR), so
I think I'll do the same thing for QEMU except I'll do Tuesday/Thursday.

For QEMU we do patches first, pull requests for reviewed stuff.
If you send a pull request out to the list the assumption is
that it's a request to apply it to master immediately.

Yep, that's the same as Linux. I just send the PR to the RISC-V mailing lists marked as an RFC so it doesn't get confused. If you don't want me to do this in QEMU land then it's fine.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]