From: kbuild test robot <lkp@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: [vfs:demo.ioctl 2/4] drivers/net//ppp/ppp_generic.c:892:46: error: 'ppp_compat_ioctl' undeclared here (not in a function); did you mean 'ppp_comp_stats'?
Date: Thu, 18 Apr 2019 23:38:41 +0800 [thread overview]
Message-ID: <201904182338.20FxtfYX%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git demo.ioctl
head: 85084dbc7e5de9a17d55e9293286604e0dac23ae
commit: a791f1d776e261a5b1e6c3b40678f2865ac2a36b [2/4] move handling of ppp filter ioctls into isdn_ppp and ppp_generic
config: i386-randconfig-x005-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout a791f1d776e261a5b1e6c3b40678f2865ac2a36b
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/net//ppp/ppp_generic.c:892:46: error: 'ppp_compat_ioctl' undeclared here (not in a function); did you mean 'ppp_comp_stats'?
.compat_ioctl = IS_ENABLED(CONFIG_COMPAT) ? ppp_compat_ioctl : NULL,
^~~~~~~~~~~~~~~~
ppp_comp_stats
vim +892 drivers/net//ppp/ppp_generic.c
885
886 static const struct file_operations ppp_device_fops = {
887 .owner = THIS_MODULE,
888 .read = ppp_read,
889 .write = ppp_write,
890 .poll = ppp_poll,
891 .unlocked_ioctl = ppp_ioctl,
> 892 .compat_ioctl = IS_ENABLED(CONFIG_COMPAT) ? ppp_compat_ioctl : NULL,
893 .open = ppp_open,
894 .release = ppp_release,
895 .llseek = noop_llseek,
896 };
897
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26117 bytes --]
reply other threads:[~2019-04-18 15:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201904182338.20FxtfYX%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).