From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paulo Alcantara <pc@cjr.nz>, Aurelien Aptel <aaptel@suse.com>,
Ronnie Sahlberg <lsahlber@redhat.com>
Subject: linux-next: build failure after merge of the cifs tree
Date: Thu, 23 Apr 2020 10:31:01 +1000 [thread overview]
Message-ID: <20200423103101.0d416eb8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
Hi all,
After merging the cifs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/cifs/connect.c: In function 'cifs_find_tcon':
fs/cifs/connect.c:3378:45: error: 'struct cifs_tcon' has no member named 'dfs_path'
3378 | if (!match_tcon(tcon, volume_info) || tcon->dfs_path)
| ^~
Caused by commit
f73409e5babd ("cifs: do not share tcons with DFS")
# CONFIG_CIFS_DFS_UPCALL is not set
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-23 0:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 0:31 Stephen Rothwell [this message]
2020-04-23 1:31 ` 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-11-10 21:57 Stephen Rothwell
2021-11-10 22:32 ` Steve French
2021-06-08 10:27 Stephen Rothwell
2021-06-08 10:53 ` Hyunchul Lee
2021-06-08 13:16 ` 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=20200423103101.0d416eb8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lsahlber@redhat.com \
--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).