From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@ozlabs.org, Nayna Jain <nayna@linux.ibm.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
linux-kernel@vger.kernel.org, Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH v3] powerpc/pseries: detect secure and trusted boot state of the system.
Date: Thu, 16 Jul 2020 22:56:05 +1000 (AEST) [thread overview]
Message-ID: <159490401795.3805857.12377577444442862197.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <1594813921-12425-1-git-send-email-nayna@linux.ibm.com>
On Wed, 15 Jul 2020 07:52:01 -0400, Nayna Jain wrote:
> The device-tree property to check secure and trusted boot state is
> different for guests(pseries) compared to baremetal(powernv).
>
> This patch updates the existing is_ppc_secureboot_enabled() and
> is_ppc_trustedboot_enabled() functions to add support for pseries.
>
> The secureboot and trustedboot state are exposed via device-tree property:
> /proc/device-tree/ibm,secure-boot and /proc/device-tree/ibm,trusted-boot
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/pseries: Detect secure and trusted boot state of the system.
https://git.kernel.org/powerpc/c/61f879d97ce4510dd29d676a20d67692e3b34806
cheers
prev parent reply other threads:[~2020-07-16 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 11:52 [PATCH v3] powerpc/pseries: detect secure and trusted boot state of the system Nayna Jain
2020-07-15 16:54 ` Mimi Zohar
2020-07-16 0:49 ` Daniel Axtens
2020-07-16 4:53 ` Michael Ellerman
2020-07-16 8:13 ` Michal Suchánek
2020-07-17 5:58 ` Daniel Axtens
2020-07-17 8:35 ` Michal Suchánek
2020-07-16 12:56 ` Michael Ellerman [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=159490401795.3805857.12377577444442862197.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=dja@axtens.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nayna@linux.ibm.com \
--cc=zohar@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).