All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Balbir Singh <bsingharora@gmail.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, Michael Neuling <mikey@neuling.org>
Subject: Re: [PATCH][V2] Add support for power9 in ibm_architecture_vec
Date: Thu, 16 Jun 2016 15:31:46 +1000	[thread overview]
Message-ID: <1466055106.5400.7.camel@ellerman.id.au> (raw)
In-Reply-To: <c624cbd5-0017-5408-a146-949f3950ba69@gmail.com>

> Subject: [PATCH][V2] Add support for power9 in ibm_architecture_vec

Can you use "[PATCH v2]", my scripts don't grok your format.

On Thu, 2016-06-16 at 14:54 +1000, Balbir Singh wrote:
> 
> On 16/06/16 10:09, Balbir Singh wrote:

> > Yes, my bad.. I'll respin. I thought I had it, but I clearly did not
> > 

Please don't send patches in replies like this, I have to manually clean the
above up before committing.
 
> V2: Update the vector length for OV1 after adding 3.0 support

This should go below the "---" line so that it's stripped from the history.

> The PVR list has been updated and IBM_ARCH_VEC_NRCORES_OFFSET.
> This provides the cpu version supported to the hypervisor

Can you give me more explanation of the practical effects of the patch. eg. This
allows guests kernels to signal to the hypervisor that they support ISA 3.0
features.

cheers

  reply	other threads:[~2016-06-16  5:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15  8:17 [PATCH] Add support for power9 in ibm_architecture_vec Balbir Singh
2016-06-15 11:17 ` Aneesh Kumar K.V
2016-06-15 12:08   ` Balbir Singh
2016-06-15 15:58     ` Aneesh Kumar K.V
2016-06-16  0:09       ` Balbir Singh
2016-06-16  4:54         ` [PATCH][V2] " Balbir Singh
2016-06-16  5:31           ` Michael Ellerman [this message]
2016-06-16  5:47             ` Balbir Singh

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=1466055106.5400.7.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=bsingharora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.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.