From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Malaterre <malat@debian.org>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>,
Laura Abbott <lauraa@codeaurora.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Gargi Sharma <gs051095@gmail.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add missing header include <linux/mem_encrypt.h>
Date: Tue, 22 May 2018 16:25:12 -0400 [thread overview]
Message-ID: <20180522162512.224b301b@gandalf.local.home> (raw)
In-Reply-To: <20180522195533.31415-1-malat@debian.org>
On Tue, 22 May 2018 21:55:31 +0200
Mathieu Malaterre <malat@debian.org> wrote:
> In commit c7753208a94c ("x86, swiotlb: Add memory encryption support") a
> call to function ‘mem_encrypt_init’ was added. Include prototype
> defined in header <linux/mem_encrypt.h> to prevent a warning reported
> during compilation with W=1:
>
> init/main.c:494:20: warning: no previous prototype for ‘mem_encrypt_init’ [-Wmissing-prototypes]
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
>
> Signed-off-by: Mathieu Malaterre <malat@debian.org>
> ---
> init/main.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/init/main.c b/init/main.c
> index 3d6b31f4e520..35ce2ddb1322 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -91,6 +91,7 @@
> #include <linux/cache.h>
> #include <linux/rodata_test.h>
> #include <linux/jump_label.h>
> +#include <linux/mem_encrypt.h>
>
> #include <asm/io.h>
> #include <asm/bugs.h>
prev parent reply other threads:[~2018-05-22 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 19:55 [PATCH] Add missing header include <linux/mem_encrypt.h> Mathieu Malaterre
2018-05-22 20:25 ` Steven Rostedt [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=20180522162512.224b301b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=gs051095@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=malat@debian.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.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).