linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Maxiwell S. Garcia" <maxiwell@linux.ibm.com>, linuxppc-dev@ozlabs.org
Cc: linux-arch@vger.kernel.org, andmike@linux.ibm.com,
	linuxram@us.ibm.com, linux-kernel@vger.kernel.org,
	kvm-ppc@vger.kernel.org, cclaudio@linux.ibm.com,
	"Maxiwell S . Garcia" <maxiwell@linux.ibm.com>,
	bauerman@linux.ibm.com
Subject: Re: [PATCH v2 1/2] powerpc: Add PowerPC Capabilities ELF note
Date: Mon,  2 Sep 2019 13:06:16 +1000 (AEST)	[thread overview]
Message-ID: <46MFN82G7vz9sDB@ozlabs.org> (raw)
In-Reply-To: <20190829155021.2915-2-maxiwell@linux.ibm.com>

On Thu, 2019-08-29 at 15:50:20 UTC, "Maxiwell S. Garcia" wrote:
> From: Claudio Carvalho <cclaudio@linux.ibm.com>
> 
> Add the PowerPC name and the PPC_ELFNOTE_CAPABILITIES type in the
> kernel binary ELF note. This type is a bitmap that can be used to
> advertise kernel capabilities to userland.
> 
> This patch also defines PPCCAP_ULTRAVISOR_BIT as being the bit zero.
> 
> Suggested-by: Paul Mackerras <paulus@ozlabs.org>
> Signed-off-by: Claudio Carvalho <cclaudio@linux.ibm.com>
> [ maxiwell: Define the 'PowerPC' type in the elfnote.h ]
> Signed-off-by: Maxiwell S. Garcia <maxiwell@linux.ibm.com>

Series applied to powerpc topic/ppc-kvm, thanks.

https://git.kernel.org/powerpc/c/70ed86f4de5bd74dd2d884dcd2f3275c4cfe665f

cheers

  reply	other threads:[~2019-09-02  3:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 15:50 [PATCH v2 0/2] powerpc: Add PowerPC Capabilities ELF note Maxiwell S. Garcia
2019-08-29 15:50 ` [PATCH v2 1/2] " Maxiwell S. Garcia
2019-09-02  3:06   ` Michael Ellerman [this message]
2019-08-29 15:50 ` [PATCH v2 2/2] docs: powerpc: Add ELF note documentation Maxiwell S. Garcia

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=46MFN82G7vz9sDB@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=andmike@linux.ibm.com \
    --cc=bauerman@linux.ibm.com \
    --cc=cclaudio@linux.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxram@us.ibm.com \
    --cc=maxiwell@linux.ibm.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 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).