From: kbuild test robot <fengguang.wu@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: [vfs:work.poll-annotations 16/20] drivers/bluetooth/hci_ldisc.c:754:17: error: two or more data types in declaration specifiers
Date: Mon, 30 Nov 2015 11:57:46 +0800 [thread overview]
Message-ID: <201511301145.t8QrduWF%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.poll-annotations
head: 57e25c0e9f495cfad818eacf944f83683b7576b3
commit: e273678a6de4dbdae89adbde4c784885f07ea968 [16/20] annotate tty
config: x86_64-randconfig-x012-201548 (attached as .config)
reproduce:
git checkout e273678a6de4dbdae89adbde4c784885f07ea968
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the vfs/work.poll-annotations HEAD 57e25c0e9f495cfad818eacf944f83683b7576b3 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
>> drivers/bluetooth/hci_ldisc.c:754:17: error: two or more data types in declaration specifiers
static __poll_t int hci_uart_tty_poll(struct tty_struct *tty,
^
vim +754 drivers/bluetooth/hci_ldisc.c
748 static ssize_t hci_uart_tty_write(struct tty_struct *tty, struct file *file,
749 const unsigned char *data, size_t count)
750 {
751 return 0;
752 }
753
> 754 static __poll_t int hci_uart_tty_poll(struct tty_struct *tty,
755 struct file *filp, poll_table *wait)
756 {
757 return 0;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23835 bytes --]
reply other threads:[~2015-11-30 3:58 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=201511301145.t8QrduWF%fengguang.wu@intel.com \
--to=fengguang.wu@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).