From: kbuild test robot <lkp@intel.com>
To: Aurelien Aptel <aaptel@suse.com>
Cc: kbuild-all@lists.01.org, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org,
Steve French <stfrench@microsoft.com>
Subject: [cifs:for-next 9/18] fs/cifs/smb2pdu.h:1616:1: error: expected identifier or '(' before '}' token
Date: Mon, 9 Mar 2020 07:29:16 +0800 [thread overview]
Message-ID: <202003090710.JxWQDUiv%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]
tree: git://git.samba.org/sfrench/cifs-2.6.git for-next
head: acbb77a85e7cd6c4ccce437ba4e9177e11a618cf
commit: 9465247ca6707ba0bc3a2772942ffeb530cc0aa5 [9/18] cifs: rename posix create rsp
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
git checkout 9465247ca6707ba0bc3a2772942ffeb530cc0aa5
# 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>
Note: the cifs/for-next HEAD acbb77a85e7cd6c4ccce437ba4e9177e11a618cf builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
In file included from fs/cifs/cifsglob.h:32:0,
from fs/cifs/cifsfs.c:46:
>> fs/cifs/smb2pdu.h:1616:1: error: expected identifier or '(' before '}' token
};
^
vim +1616 fs/cifs/smb2pdu.h
730928c8f4be88 Ronnie Sahlberg 2018-08-08 1605
ab3459d8f0ef52 Steve French 2020-02-06 1606 /* equivalent of the contents of SMB3.1.1 POSIX open context response */
9465247ca6707b Aurelien Aptel 2020-02-08 1607 struct create_posix_rsp {
ab3459d8f0ef52 Steve French 2020-02-06 1608 __le32 nlink;
ab3459d8f0ef52 Steve French 2020-02-06 1609 __le32 reparse_tag;
ab3459d8f0ef52 Steve French 2020-02-06 1610 __le32 mode;
9465247ca6707b Aurelien Aptel 2020-02-08 1611 /*
9465247ca6707b Aurelien Aptel 2020-02-08 1612 * var sized owner SID
9465247ca6707b Aurelien Aptel 2020-02-08 1613 * var sized group SID
9465247ca6707b Aurelien Aptel 2020-02-08 1614 */
9465247ca6707b Aurelien Aptel 2020-02-08 1615 } __packed;
ab3459d8f0ef52 Steve French 2020-02-06 @1616 };
:::::: The code at line 1616 was first introduced by commit
:::::: ab3459d8f0ef52c38119ed58c4c29139efc7022c smb3: print warning once if posix context returned on open
:::::: TO: Steve French <stfrench@microsoft.com>
:::::: CC: Steve French <stfrench@microsoft.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 71471 bytes --]
reply other threads:[~2020-03-08 23:30 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=202003090710.JxWQDUiv%lkp@intel.com \
--to=lkp@intel.com \
--cc=aaptel@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=stfrench@microsoft.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 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).