On Wed, 16 Nov 2016 09:17:43 +1100
David Gibson wrote:
> This series is a significant rework to how we handle CPU compatibility
> modes on ppc.
>
David,
Please find below the results of the migration tests.
> * Information about compatibility modes was previously open coded and
>scattere
On Sat, Nov 26, 2016 at 01:33:16AM +0100, Greg Kurz wrote:
> On Wed, 16 Nov 2016 09:17:43 +1100
> David Gibson wrote:
>
> > This series is a significant rework to how we handle CPU compatibility
> > modes on ppc.
> >
> > * Information about compatibility modes was previously open coded and
> >
On Mon, Nov 28, 2016 at 03:23:46PM +1100, David Gibson wrote:
> On Sat, Nov 26, 2016 at 01:33:16AM +0100, Greg Kurz wrote:
> > On Wed, 16 Nov 2016 09:17:43 +1100
> > David Gibson wrote:
> >
> > > This series is a significant rework to how we handle CPU compatibility
> > > modes on ppc.
> > >
> >
On Wed, 16 Nov 2016 09:17:43 +1100
David Gibson wrote:
> This series is a significant rework to how we handle CPU compatibility
> modes on ppc.
>
> * Information about compatibility modes was previously open coded and
>scattered across a number of functions in both target-ppc and spapr
>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [RFCv2 00/12] Clean up compatibility mode handling
Message-id: 1479248275-18889-1-git-send-email-da...@gibson.dropbear.id.au
=== TEST SCRIPT BEGIN ===
#!/bin/bash
This series is a significant rework to how we handle CPU compatibility
modes on ppc.
* Information about compatibility modes was previously open coded and
scattered across a number of functions in both target-ppc and spapr
code. It's now brought together into a common table of
compatibi
