From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Morris <jmorris@namei.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
David Safford <safford@watson.ibm.com>
Subject: Re: linux-next: build failure after merge of the final tree (security-testing tree related)
Date: Mon, 29 Nov 2010 13:57:58 +1100 [thread overview]
Message-ID: <20101129135758.342fb940.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20101129132520.6884a624.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]
[Forgot to send this top James]
On Mon, 29 Nov 2010 13:25:20 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the final tree, today's linux-next build (powerpc allyesconfig)
> failed like this:
>
> security/keys/trusted_defined.c: In function 'init_sdesc':
> security/keys/trusted_defined.c:52: error: implicit declaration of function 'ERR_PTR'
> security/keys/trusted_defined.c:52: warning: return makes pointer from integer without a cast
> security/keys/trusted_defined.c: In function 'TSS_sha1':
> security/keys/trusted_defined.c:65: error: implicit declaration of function 'IS_ERR'
> security/keys/trusted_defined.c:67: error: implicit declaration of function 'PTR_ERR'
> make[3]: *** [security/keys/trusted_defined.o] Error 1
> security/keys/encrypted_defined.c: In function 'aes_get_sizes':
> security/keys/encrypted_defined.c:73: error: implicit declaration of function 'IS_ERR'
> security/keys/encrypted_defined.c:74: error: implicit declaration of function 'PTR_ERR'
> security/keys/encrypted_defined.c:74: warning: format '%ld' expects type 'long int', but argument 2 has type 'int'
> security/keys/encrypted_defined.c: In function 'init_sdesc':
> security/keys/encrypted_defined.c:270: error: implicit declaration of function 'ERR_PTR'
> security/keys/encrypted_defined.c:270: warning: return makes pointer from integer without a cast
> security/keys/encrypted_defined.c: In function 'init_blkcipher_desc':
> security/keys/encrypted_defined.c:351: warning: format '%ld' expects type 'long int', but argument 3 has type 'int'
> security/keys/encrypted_defined.c: In function 'encrypted_key_alloc':
> security/keys/encrypted_defined.c:536: warning: return makes pointer from integer without a cast
> security/keys/encrypted_defined.c:547: warning: return makes pointer from integer without a cast
> security/keys/encrypted_defined.c:552: warning: return makes pointer from integer without a cast
>
> Caused by commits d00a1c72f7f4661212299e6cb132dfa58030bcdb ("keys: add new
> trusted key-type") and 7e70cb4978507cf31d76b90e4cfb4c28cad87f0c ("keys:
> add new key-type encrypted"). Missing include(s). See Rule 1 in
> Documentation/SubmitChecklist.
>
> I have reverted those commits for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-11-29 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 2:25 linux-next: build failure after merge of the final tree (security-testing tree related) Stephen Rothwell
2010-11-29 2:25 ` Stephen Rothwell
2010-11-29 2:57 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-16 14:05 Stephen Rothwell
2010-10-20 5:10 Stephen Rothwell
2010-10-20 11:46 ` Eric Paris
2010-10-20 22:28 ` James Morris
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=20101129135758.342fb940.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=safford@watson.ibm.com \
--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 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.