From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34212) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZuJ9t-0004hg-B5 for qemu-devel@nongnu.org; Thu, 05 Nov 2015 06:56:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZuJ9p-00043O-Aw for qemu-devel@nongnu.org; Thu, 05 Nov 2015 06:56:49 -0500 Received: from mail-pa0-x229.google.com ([2607:f8b0:400e:c03::229]:33517) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZuJ9p-000435-34 for qemu-devel@nongnu.org; Thu, 05 Nov 2015 06:56:45 -0500 Received: by pabfh17 with SMTP id fh17so86095132pab.0 for ; Thu, 05 Nov 2015 03:56:44 -0800 (PST) References: <1446697838-10607-1-git-send-email-aik@ozlabs.ru> From: Alexey Kardashevskiy Message-ID: <563B43F6.7080702@ozlabs.ru> Date: Thu, 5 Nov 2015 22:56:38 +1100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [GIT PULL qemu v2] pseries: Update SLOF firmware image to qemu-slof-20151103 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "qemu-ppc@nongnu.org" , QEMU Developers , David Gibson On 11/05/2015 10:47 PM, Peter Maydell wrote: > On 5 November 2015 at 04:30, Alexey Kardashevskiy wrote: >> Hi! >> >> This is a SLOF update which is 700k and therefore too big to be posted >> as a patch so here is a pull request. >> >> Changes: >> v2: >> * rebuilt with gcc 4.8, v1 was build with 5.2.1 by mistake >> >> >> The following changes since commit 90da0d5a703839c8db9f37355107955df043b654: >> >> ppc/spapr: Add "ibm,pa-features" property to the device-tree (2015-10-23 12:22:40 +1100) >> >> are available in the git repository at: >> >> git@github.com:aik/qemu.git slof-20151103 >> >> for you to fetch changes up to d95c5ce2f99f8f2328b288a63fed4f006519be6d: >> >> pseries: Update SLOF firmware image to qemu-slof-20151103 (2015-11-05 15:26:08 +1100) > > I'm assuming you're expecting this to go via the ppc tree, rather > than directly applied to master. I believe so. I am just not sure through which tree exactly - David's spapr-next or Alex's ppc-next. -- Alexey