qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [GIT PULL qemu v2] pseries: Update SLOF firmware image to qemu-slof-20151103
Date: Thu, 5 Nov 2015 22:56:38 +1100	[thread overview]
Message-ID: <563B43F6.7080702@ozlabs.ru> (raw)
In-Reply-To: <CAFEAcA_KpXqESgHo1oD+o8fdHWqKpZFWzUYjYqbNq8=J3wTOvQ@mail.gmail.com>

On 11/05/2015 10:47 PM, Peter Maydell wrote:
> On 5 November 2015 at 04:30, Alexey Kardashevskiy <aik@ozlabs.ru> 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

      reply	other threads:[~2015-11-05 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  4:30 [Qemu-devel] [GIT PULL qemu v2] pseries: Update SLOF firmware image to qemu-slof-20151103 Alexey Kardashevskiy
2015-11-05 11:47 ` Peter Maydell
2015-11-05 11:56   ` Alexey Kardashevskiy [this message]

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=563B43F6.7080702@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /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).