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:work.tty-ioctl 49/50] drivers/tty/pty.c:688:41: error: implicit declaration of function 'compat_ptr'
Date: Thu, 13 Sep 2018 10:06:47 +0800 [thread overview]
Message-ID: <201809131044.EdhC3yZz%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.tty-ioctl
head: 5813bfc971394b8bab482bbb4f26a68d34c6cfb3
commit: 6c8b7b17bd0d9cc3e5d5b1f644fa98227b32e0ab [49/50] pty: fix compat ioctls
config: openrisc-or1ksim_defconfig (attached as .config)
compiler: or1k-linux-gcc (GCC) 6.0.0 20160327 (experimental)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 6c8b7b17bd0d9cc3e5d5b1f644fa98227b32e0ab
# save the attached .config to linux build tree
make.cross ARCH=openrisc
All errors (new ones prefixed by >>):
drivers/tty/pty.c: In function 'pty_unix98_compat_ioctl':
>> drivers/tty/pty.c:688:41: error: implicit declaration of function 'compat_ptr' [-Werror=implicit-function-declaration]
cmd == TIOCSIG ? arg : (unsigned long)compat_ptr(arg));
^~~~~~~~~~
cc1: some warnings being treated as errors
vim +/compat_ptr +688 drivers/tty/pty.c
679
680 static long pty_unix98_compat_ioctl(struct tty_struct *tty,
681 unsigned int cmd, unsigned long arg)
682 {
683 /*
684 * PTY ioctls don't require any special translation between 32-bit and
685 * 64-bit userspace, they are already compatible.
686 */
687 return pty_unix98_ioctl(tty, cmd,
> 688 cmd == TIOCSIG ? arg : (unsigned long)compat_ptr(arg));
689 }
690
---
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: 7798 bytes --]
reply other threads:[~2018-09-13 7:15 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=201809131044.EdhC3yZz%fengguang.wu@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).