From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
Cc: "Paulo Alcantara (SUSE)" <pc@cjr.nz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the cifs tree
Date: Thu, 11 Nov 2021 08:57:46 +1100 [thread overview]
Message-ID: <20211111085746.46746d4f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
Hi all,
After merging the cifs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
<stdin>:1559:2: warning: #warning syscall futex_waitv not implemented [-Wcpp]
fs/cifs/connect.c: In function 'clean_demultiplex_info':
fs/cifs/connect.c:841:2: error: stray '#' in program
841 | +#ifdef CONFIG_CIFS_DFS_UPCALL
| ^
fs/cifs/connect.c:841:3: error: 'ifdef' undeclared (first use in this function)
841 | +#ifdef CONFIG_CIFS_DFS_UPCALL
| ^~~~~
fs/cifs/connect.c:841:3: note: each undeclared identifier is reported only once for each function it appears in
fs/cifs/connect.c:841:8: error: expected ';' before 'CONFIG_CIFS_DFS_UPCALL'
841 | +#ifdef CONFIG_CIFS_DFS_UPCALL
| ^~~~~~~~~~~~~~~~~~~~~~~
| ;
fs/cifs/connect.c:843:15: error: 'struct TCP_Server_Info' has no member named 'leaf_fullpath'
843 | + kfree(server->leaf_fullpath);
| ^~
fs/cifs/connect.c:844:2: error: stray '#' in program
844 | +#endif
| ^
fs/cifs/connect.c:844:3: error: 'endif' undeclared (first use in this function); did you mean 'gendisk'?
844 | +#endif
| ^~~~~
| gendisk
fs/cifs/connect.c:844:8: error: expected ';' before 'kfree'
844 | +#endif
| ^
| ;
845 | kfree(server);
| ~~~~~
Caused by commit
58b90aa95977 ("cifs: support nested dfs links over reconnect")
I have used the cifs tree from next-20211110 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-11-10 21:57 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 21:57 Stephen Rothwell [this message]
2021-11-10 22:32 ` linux-next: build failure after merge of the cifs tree Steve French
-- strict thread matches above, loose matches on Subject: below --
2024-03-19 22:59 Stephen Rothwell
2024-03-19 23:37 ` Steve French
2023-07-20 0:35 Stephen Rothwell
2023-07-20 0:47 ` Steve French
2023-07-20 1:00 ` Stephen Rothwell
2023-07-20 1:33 ` Winston Wen
2021-11-15 22:17 Stephen Rothwell
2021-11-15 22:35 ` Steve French
2021-06-08 10:27 Stephen Rothwell
2021-06-08 10:53 ` Hyunchul Lee
2021-06-08 13:16 ` Steve French
2020-04-23 0:31 Stephen Rothwell
2020-04-23 1:31 ` Steve French
2018-06-24 23:15 Stephen Rothwell
2018-06-25 0:52 ` Steve French
2018-06-01 0:09 Stephen Rothwell
2018-06-01 0:19 ` Steve French
2017-09-26 0:51 Stephen Rothwell
2017-09-26 1:20 ` Steve French
2016-11-29 22:27 Stephen Rothwell
2016-12-01 6:27 ` Steve French
2012-08-06 0:48 Stephen Rothwell
2012-08-06 1:57 ` Steve French
2012-01-19 0:01 Stephen Rothwell
2012-01-19 0:31 ` Steve French
2011-10-25 13:59 Stephen Rothwell
2011-10-25 14:51 ` Steve French
2011-10-25 15:05 ` Steve French
2011-10-25 15:58 ` Jeff Layton
2011-10-25 15:55 ` Jeff Layton
2011-03-10 0:43 Stephen Rothwell
2011-03-10 1:03 ` Steve French
2010-09-23 1:20 Stephen Rothwell
2010-09-23 1:32 ` Steve French
2010-09-23 1:47 ` Steve French
2010-08-12 3:17 Stephen Rothwell
2010-08-12 4:04 ` Steve French
2010-08-12 7:46 ` Stephen Rothwell
2010-08-12 15:18 ` Bryan Schumaker
2010-08-12 18:21 ` Steve French
2010-08-12 15:24 ` David Howells
2010-07-15 23:51 Stephen Rothwell
2010-07-16 4:34 ` Steve French
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=20211111085746.46746d4f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pc@cjr.nz \
--cc=smfrench@gmail.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).