All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: open@suse.de, "list@suse.de:PowerPC" <qemu-ppc@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"Prerna Saxena" <prerna@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/4] target-ppc: Fill in OpenFirmware names for some PowerPCCPU families
Date: Mon, 30 Sep 2013 19:55:35 +0200	[thread overview]
Message-ID: <5249BB17.60800@suse.de> (raw)
In-Reply-To: <5242A677.9090809@ozlabs.ru>

On 09/25/2013 11:01 AM, Alexey Kardashevskiy wrote:
> On 09/17/2013 12:16 AM, Alexey Kardashevskiy wrote:
>> On 09/10/2013 02:15 PM, Alexey Kardashevskiy wrote:
>>> On 08/16/2013 08:35 AM, Andreas Färber wrote:
>>>> Set the expected values for POWER7, POWER7+, POWER8 and POWER5+.
>>>> Note that POWER5+ and POWER7+ are intentionally lacking the '+', so the
>>>> lack of a POWER7P family constitutes no problem.
>>>>
>>>> Signed-off-by: Andreas Färber<afaerber@suse.de>
>>>
>>> Out of curiosity - is anything going to happen to this series? Is it
>>> awaiting for someone's review? Just asking as it is quite old and nobody
>>> seems to care :)
>> Ping, anyone? Not sure if any of my mails even reaches maillists :-/
> Ping?
>
> It conflicts with "[PATCH] pseries: Fix loading of little endian kernels"
> posted today. It would be great to have either this series or the new patch
> upstream...

Andreas is going to rework it, yes :).


Alex

  reply	other threads:[~2013-09-30 17:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 22:35 [Qemu-devel] [PATCH v2 0/4] target-ppc: Tidy sPAPR device tree CPU nodes Andreas Färber
2013-08-15 22:35 ` [Qemu-devel] [PATCH v2 1/4] target-ppc: Fill in OpenFirmware names for some PowerPCCPU families Andreas Färber
2013-09-10  4:15   ` Alexey Kardashevskiy
2013-09-16 14:16     ` Alexey Kardashevskiy
2013-09-25  9:01       ` Alexey Kardashevskiy
2013-09-30 17:55         ` Alexander Graf [this message]
2013-10-07 13:59           ` Alexey Kardashevskiy
2013-08-15 22:35 ` [Qemu-devel] [PATCH v2 2/4] spapr: Use DeviceClass::fw_name for device tree CPU node Andreas Färber
2013-08-29  4:29   ` Alexey Kardashevskiy
2013-08-29  5:30     ` Andreas Färber
2013-08-30  6:05       ` Alexey Kardashevskiy
2013-08-30 13:54         ` Alexander Graf
2013-08-30 14:00           ` Andreas Färber
2013-08-30 14:15             ` Alexander Graf
2013-08-30 13:21   ` Alexander Graf
2013-08-30 13:26     ` Andreas Färber
2013-08-30 13:52       ` Alexander Graf
2013-08-30 13:53       ` Alexey Kardashevskiy
2013-08-30 13:58         ` Andreas Färber
2013-08-30 14:03           ` Alexander Graf
2013-08-15 22:35 ` [Qemu-devel] [PATCH v2 3/4] spapr: Improve device tree CPU node for -cpu host with unknown OF name Andreas Färber
2013-08-15 22:40   ` Andreas Färber
2013-08-29  4:33   ` [Qemu-devel] [Qemu-ppc] " Alexey Kardashevskiy
2013-08-29  5:30     ` Andreas Färber
2013-08-15 22:35 ` [Qemu-devel] [PATCH v2 4/4] spapr: Suppress underscores in device tree CPU node Andreas Färber
2013-08-29  4:39   ` [Qemu-devel] [Qemu-ppc] " Alexey Kardashevskiy
2013-08-29  5:33     ` Andreas Färber

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=5249BB17.60800@suse.de \
    --to=agraf@suse.de \
    --cc=afaerber@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=open@suse.de \
    --cc=prerna@linux.vnet.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.