From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Clark <mjc@sifive.com>
Cc: qemu-devel@nongnu.org,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Palmer Dabbelt <palmer@sifive.com>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
RISC-V Patches <patches@groups.riscv.org>
Subject: Re: [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8.2
Date: Thu, 8 Mar 2018 12:25:49 +0000 [thread overview]
Message-ID: <20180308122549.GO4718@redhat.com> (raw)
In-Reply-To: <1520365586-30384-1-git-send-email-mjc@sifive.com>
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 :|
next prev parent reply other threads:[~2018-03-08 12:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 19:46 [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8.2 Michael Clark
2018-03-07 0:09 ` Michael Clark
2018-03-07 10:11 ` Richard W.M. Jones
2018-03-07 12:15 ` Michael Clark
2018-03-08 10:02 ` Peter Maydell
2018-03-08 11:10 ` Michael Clark
2018-03-08 11:18 ` Michael Clark
2018-03-08 11:41 ` Michael Clark
2018-03-08 11:52 ` Stefan Hajnoczi
2018-03-08 19:29 ` [Qemu-devel] [patches] " Palmer Dabbelt
2018-03-08 19:53 ` Michael Clark
2018-03-09 14:28 ` Peter Maydell
2018-03-09 14:51 ` Michael Clark
2018-03-09 15:15 ` Alex Bennée
2018-03-09 15:22 ` Peter Maydell
2018-03-09 16:49 ` Peter Maydell
2018-03-09 20:11 ` Michael Clark
2018-03-09 20:23 ` Michael Clark
2018-03-08 11:48 ` [Qemu-devel] " Daniel P. Berrangé
2018-03-08 20:03 ` Michael Clark
2018-03-08 11:49 ` Paolo Bonzini
2018-03-08 11:19 ` Peter Maydell
2018-03-08 11:36 ` Daniel P. Berrangé
2018-03-08 11:33 ` Daniel P. Berrangé
2018-03-08 11:42 ` Daniel P. Berrangé
2018-03-08 12:25 ` Daniel P. Berrangé [this message]
2018-03-08 12:39 ` Paolo Bonzini
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=20180308122549.GO4718@redhat.com \
--to=berrange@redhat.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.org \
--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).