qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8.2


From: Daniel P . Berrangé
Subject: Re: [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8.2
Date: Thu, 8 Mar 2018 12:25:49 +0000
User-agent: Mutt/1.9.2 (2017-12-15)

On Wed, Mar 07, 2018 at 08:46:26AM +1300, Michael Clark wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> The following changes since commit f32408f3b472a088467474ab152be3b6285b2d7b:
> 
>   misc: don't use hwaddr as a type in trace events (2018-03-06 14:24:30 +0000)
> 
> are available in the git repository at:
> 
>   https://github.com/riscv/riscv-qemu.git tags/riscv-qemu-upstream-v8.2
> 
> for you to fetch changes up to 7051b081bf6796e5e84406f6223a7c4900bf7298:
> 
>   RISC-V - Remove support for adhoc non-standard X_COP local-interrupt 
> (2018-03-07 08:36:03 +1300)

So to move this forward in a productive way....

IIUC, the 'qemu-upstream-v8.2' branch has the correct set of 23
patches, but the 'riscv-qemu-upstream-v8.2' tag has mistakenly
gained a bunch of extra patches that were not intended for
submission yet.

So I think you likely just need to create a v8.3 branch and
tag with the correct set of 23 commits. Though, do note Paolo's
comment about logic looking wrong in one of the patches. I'm
not sure if that's something we can live with now, and fix
up in followup patches before release or not, vs should be
fixed right away.

The 'soft freeze' on next Tuesday only applies to feature
patches. So assuming we can get this initial series mergable,
you will still have time to send more pull requests with bug
fixes before release.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



reply via email to

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