All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: Derek Straka <derek@asterius.io>, xen-devel@lists.xenproject.org
Cc: andrew.cooper3@citrix.com, gang.wei@intel.com, jbeulich@suse.com,
	shane.wang@intel.com
Subject: Re: [PATCHv2] x86: Add a tboot Kconfig option
Date: Thu, 18 Aug 2016 19:04:54 -0500	[thread overview]
Message-ID: <db5557a5-3ce9-4b73-e894-f5a66ea17813@cardoe.com> (raw)
In-Reply-To: <1471563865-30163-1-git-send-email-derek@asterius.io>


[-- Attachment #1.1.1: Type: text/plain, Size: 877 bytes --]

On 8/18/16 6:44 PM, Derek Straka wrote:
> Allows for the conditional inclusion of tboot related functionality
> via Kconfig
> 
> The default configuration for the new CONFIG_TBOOT option is 'y', so the
> behavior out of the box remains unchanged.  The addition of the option allows
> advanced users to disable system behaviors associated with tboot at compile
> time rather than relying on the run-time detection and configuration.
> 
> The CONFIG_CRYPTO option is 'n' by default and selected by the individual users
> that require the functionality.  Currently, the only user is tboot.
> 
> Signed-off-by: Derek Straka <derek@asterius.io>
> ---

Reviewed-by: Doug Goldstein <cardoe@cardoe.com>


>  
> +config CRYPTO
> +	bool
> +	default n
> +

If a v3 happens (or the committer wants to change it) this can be
"def_bool n".

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-08-19  0:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 23:44 [PATCHv2] x86: Add a tboot Kconfig option Derek Straka
2016-08-19  0:04 ` Doug Goldstein [this message]
2016-08-19  7:47   ` Jan Beulich

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=db5557a5-3ce9-4b73-e894-f5a66ea17813@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=derek@asterius.io \
    --cc=gang.wei@intel.com \
    --cc=jbeulich@suse.com \
    --cc=shane.wang@intel.com \
    --cc=xen-devel@lists.xenproject.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.