All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Mihai Caraman <mihai.caraman@freescale.com>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Remove shared defines for SPE and AltiVec interrupts
Date: Mon, 01 Sep 2014 22:43:55 +0000	[thread overview]
Message-ID: <5404F6AB.8090302@suse.de> (raw)
In-Reply-To: <1409566663-16152-1-git-send-email-mihai.caraman@freescale.com>



On 01.09.14 12:17, Mihai Caraman wrote:
> We currently decide at compile-time which of the SPE or AltiVec units to
> support exclusively. Guard kernel defines with CONFIG_SPE_POSSIBLE and
> CONFIG_PPC_E500MC and remove shared defines.
> 
> Signed-off-by: Mihai Caraman <mihai.caraman@freescale.com>

Thanks, applied to kvm-ppc-queue.


Alex

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Mihai Caraman <mihai.caraman@freescale.com>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Remove shared defines for SPE and AltiVec interrupts
Date: Tue, 02 Sep 2014 00:43:55 +0200	[thread overview]
Message-ID: <5404F6AB.8090302@suse.de> (raw)
In-Reply-To: <1409566663-16152-1-git-send-email-mihai.caraman@freescale.com>



On 01.09.14 12:17, Mihai Caraman wrote:
> We currently decide at compile-time which of the SPE or AltiVec units to
> support exclusively. Guard kernel defines with CONFIG_SPE_POSSIBLE and
> CONFIG_PPC_E500MC and remove shared defines.
> 
> Signed-off-by: Mihai Caraman <mihai.caraman@freescale.com>

Thanks, applied to kvm-ppc-queue.


Alex

  reply	other threads:[~2014-09-01 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 10:17 [PATCH] KVM: PPC: Remove shared defines for SPE and AltiVec interrupts Mihai Caraman
2014-09-01 10:17 ` Mihai Caraman
2014-09-01 22:43 ` Alexander Graf [this message]
2014-09-01 22:43   ` Alexander Graf

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=5404F6AB.8090302@suse.de \
    --to=agraf@suse.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mihai.caraman@freescale.com \
    /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.