From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warnings after merge of the keys tree
Date: Mon, 13 Nov 2017 13:10:56 +1100 [thread overview]
Message-ID: <20171113131056.14b3f4da@canb.auug.org.au> (raw)
Hi David,
After merging the keys tree, today's linux-next build (arm
multi_v7_defconfiga) produced these warning:
certs/system_keyring.c:39:23: warning: 'trusted_keyring_acl' defined but not used [-Wunused-variable]
static struct key_acl trusted_keyring_acl = {
^
net/wireless/reg.c: In function 'load_keys_from_buffer':
net/wireless/reg.c:688:9: warning: passing argument 6 of 'key_create_or_update' makes pointer from integer without a cast [-Wint-conversion]
((KEY_POS_ALL & ~KEY_POS_SETATTR) |
^
In file included from include/linux/cred.h:17:0,
from include/linux/seq_file.h:12,
from include/linux/pinctrl/consumer.h:17,
from include/linux/pinctrl/devinfo.h:21,
from include/linux/device.h:24,
from include/linux/platform_device.h:14,
from net/wireless/reg.c:55:
include/linux/key.h:297:18: note: expected 'struct key_acl *' but argument is of type 'int'
extern key_ref_t key_create_or_update(key_ref_t keyring,
^
net/wireless/reg.c: In function 'load_builtin_regdb_keys':
net/wireless/reg.c:715:10: warning: passing argument 5 of 'keyring_alloc' makes pointer from integer without a cast [-Wint-conversion]
((KEY_POS_ALL & ~KEY_POS_SETATTR) |
^
In file included from include/linux/cred.h:17:0,
from include/linux/seq_file.h:12,
from include/linux/pinctrl/consumer.h:17,
from include/linux/pinctrl/devinfo.h:21,
from include/linux/device.h:24,
from include/linux/platform_device.h:14,
from net/wireless/reg.c:55:
include/linux/key.h:315:20: note: expected 'struct key_acl *' but argument is of type 'int'
extern struct key *keyring_alloc(const char *description, kuid_t uid, kgid_t gid,
^
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-11-13 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 2:10 Stephen Rothwell [this message]
2017-11-13 9:42 ` linux-next: build warnings after merge of the keys tree David Howells
2019-07-30 2:30 Stephen Rothwell
2019-07-30 3:47 ` Eric Biggers
2019-07-30 3:52 ` Stephen Rothwell
2019-07-31 1:40 ` Eric Biggers
2019-07-31 3:05 ` Stephen Rothwell
2020-05-04 3:47 Stephen Rothwell
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=20171113131056.14b3f4da@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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).