[Top][All Lists]

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

Re: [Qemu-devel] [PATCH v3 00/23] target/openrisc improvements

From: Peter Maydell
Subject: Re: [Qemu-devel] [PATCH v3 00/23] target/openrisc improvements
Date: Mon, 2 Jul 2018 13:27:17 +0100

On 28 June 2018 at 22:31, Stafford Horne <address@hidden> wrote:
> On Wed, Jun 27, 2018 at 08:03:07PM -0700, Richard Henderson wrote:
>> Changes since v2:
>>   * Fix missing mtspr break.
>>   * Reorg print_insn_or1k and interrupt logging to the start.
>>   * Adjust exit after mtspr; fixing smp kernel crash.
>>   * Fix signals patch based on Larent's review.
> Thanks, I confirmed this is working for me too.
> As mentioned before there are a few items I am working on.  I will take the
> series and send the pull request during the merge window.

QEMU doesn't have "merge windows". We just have a softfreeze
date. During the "general development" part of the release
cycle, send pullrequests whenever you like, for new features,
bugfixes, etc. Prefer "little and often" rather than saving
up lots of patches and sending huge pull requests infrequently.

The last pullrequests before softfreeze need to be on the
mailing list by the softfreeze date. After softfreeze, only
bug fixes should be submitted. We get gradually stricter
about how bad the bug has to be to justify allowing in a
fix as we go along; so in rc1 we're fairly relaxed about
larger changes that fix bugs, and by the time we get to
rc3 or rc4 we really only want safe small changes that
fix bugs that are regressions from the previous release.

Pull request cover letters during the freeze part of the
release cycle should include enough detail about the bugs
being fixed to let me judge whether they match the criteria
for going into the next rc, especially at the end of the cycle.

-- PMM

reply via email to

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