From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>, xen-devel@lists.xenproject.org
Cc: julien.grall@linaro.org, wei.liu2@citrix.com, ian.campbell@citrix.com
Subject: Re: [PATCH 1/2] flask: clean up initialization and #defines
Date: Mon, 9 Mar 2015 11:00:13 +0000 [thread overview]
Message-ID: <54FD7D3D.7040706@citrix.com> (raw)
In-Reply-To: <1425678216-26823-2-git-send-email-dgdegra@tycho.nsa.gov>
On 06/03/15 21:43, Daniel De Graaf wrote:
> This removes the FLASK_DEVELOP and FLASK_BOOTPARAM configuration
> parameters which have never been settable by users. Disabling the
> FLASK_DEVELOP configuration option has not produced a compiling
> hypervisor for some time, and the FLASK_BOOTPARAM option will be
> replaced with a more flexible boot parameter.
>
> This also changes the return type of xsm_initcall_t to void to properly
> reflect the fact that the caller ignores the return value.
>
> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
> Reviewed-by: Wei Liu <wei.liu2@citrix.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2015-03-09 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 21:43 [PATCH v4 0/2] flask: Handle policy load failures properly Daniel De Graaf
2015-03-06 21:43 ` [PATCH 1/2] flask: clean up initialization and #defines Daniel De Graaf
2015-03-09 11:00 ` Andrew Cooper [this message]
2015-03-06 21:43 ` [PATCH 2/2] flask: create unified "flask=" boot parameter Daniel De Graaf
2015-03-09 11:19 ` Andrew Cooper
2015-03-09 12:25 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2015-03-03 17:00 [PATCH v3 0/2] flask: Handle policy load failures properly Daniel De Graaf
2015-03-03 17:00 ` [PATCH 1/2] flask: clean up initialization and #defines Daniel De Graaf
2015-03-06 12:15 ` Wei Liu
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=54FD7D3D.7040706@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=wei.liu2@citrix.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.