On Sat, Jun 23, 2018 at 07:43:04AM +0100, Mark Cave-Ayland wrote: > On 23/06/18 01:41, David Gibson wrote: > > > On Fri, Jun 22, 2018 at 04:16:10PM +0100, Mark Cave-Ayland wrote: > > 11;rgb:ffff/ffff/ffff> On 22/06/18 16:03, Peter Maydell wrote: > > > > > > > On 22 June 2018 at 11:35, David Gibson <da...@gibson.dropbear.id.au> > > > > wrote: > > > > > The following changes since commit > > > > > 46012db666990ff2eed1d3dc199ab8006439a93b: > > > > > > > > > > Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20180619' > > > > > into staging (2018-06-20 09:51:30 +0100) > > > > > > > > > > are available in the Git repository at: > > > > > > > > > > git://github.com/dgibson/qemu.git tags/ppc-for-3.0-20180622 > > > > > > > > > > for you to fetch changes up to > > > > > e5ca28ecab5c69b7578e22391a66c97c3979ffd8: > > > > > > > > > > spapr: Don't rewrite mmu capabilities in KVM mode (2018-06-22 > > > > > 14:19:07 +1000) > > > > > > > > > > ---------------------------------------------------------------- > > > > > ppc patch queue 2018-06-22 > > > > > > > > > > Another assorted patch of patches for ppc and spapr. > > > > > * Rework of guest pagesize handling for ppc, which avoids guest > > > > > visibly different behaviour between accelerators > > > > > * A number of Pnv cleanups, working towards more complete POWER9 > > > > > support > > > > > * Migration of VPA data, a significant bugfix > > > > > > > > Applied, thanks. > > > > > > > > -- PMM > > > > > > Looks like this is missing the 2 Mac commits I submitted that David added > > > to > > > the PR this morning? > > > > > > https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg06540.html > > > https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg06536.html > > > > > > David, did you forget to re-push the updated tag? > > > > They just missed the window, sorry. I merged them after I'd already > > tagged and tested the pull request. > > Okay, as long as you didn't forget them :) > > My confusion came from the fact that the emails you sent for the PR > yesterday contained my patches as patches 24 and 25, although they aren't > included in the cover letter or the github tag.
Ah, right. So I realized that bogus set of mails was the result of
pointing git send-email at a git range instead of the batch of mails
already prepared for the pull request. Which meant for one they
weren't properly formatted for a PR, and also it included the couple
of patches of yours I'd applied after tagging the PR.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
signature.asc
Description: PGP signature
