From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: zohar@linux.vnet.ibm.com, jim.epost@gmail.com
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, james.l.morris@oracle.com,
linux-security-module@vger.kernel.org
Subject: Re: randconfig build error with next-20131104, in security/integrity
Date: Tue, 5 Nov 2013 21:12:26 +0900 [thread overview]
Message-ID: <201311052112.DCC60296.MFOOFSOHJVtLQF@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <1383606829.15186.25.camel@dhcp-9-2-203-236.watson.ibm.com>
Mimi Zohar wrote:
> @@ -132,24 +133,22 @@ static inline int integrity_digsig_verify(const unsigned int id,
> return -EOPNOTSUPP;
> }
>
> +static int integrity_init_keyring(const unsigned int id)
Please add inline keyword, or compiler makes noisy warning.
> +{
> + return 0;
> +}
> #endif /* CONFIG_INTEGRITY_SIGNATURE */
next prev parent reply other threads:[~2013-11-05 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 18:29 randconfig build error with next-20131104, in security/integrity Jim Davis
2013-11-04 23:13 ` Mimi Zohar
2013-11-05 12:12 ` Tetsuo Handa [this message]
2013-11-05 12:55 ` Mimi Zohar
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=201311052112.DCC60296.MFOOFSOHJVtLQF@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=james.l.morris@oracle.com \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=zohar@linux.vnet.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).