From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steve French <smfrench@gmail•com>, linux-cifs-client@lists•samba.org
Cc: linux-next@vger•kernel.org, Al Viro <viro@zeniv•linux.org.uk>,
Shirish Pargaonkar <shirishp@us•ibm.com>
Subject: linux-next: cifs tree build failure
Date: Tue, 14 Apr 2009 11:41:53 +1000 [thread overview]
Message-ID: <20090414114153.00467d45.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
Hi Steve,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
fs/cifs/dir.c: In function 'cifs_lookup':
fs/cifs/dir.c:664: error: dereferencing pointer to incomplete type
Caused by commit 84c63ad9195b37b3de43427c11471a763c3993cc ("[CIFS] Add
support for posix open during lookup") from the cifs tree (probably an
interaction with commit 5ad4e53bd5406ee214ddc5a41f03f779b8b2d526 ("Get
rid of indirect include of fs_struct.h") - now in Linus' tree).
I have used the cifs tree from next-20090409 for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-04-14 1:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 1:41 Stephen Rothwell [this message]
2009-04-15 2:59 ` linux-next: cifs tree build failure Stephen Rothwell
2009-04-15 3:10 ` Steve French
2009-04-15 3:20 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 3:32 Stephen Rothwell
2009-06-15 10:46 ` Jeff Layton
2009-06-15 13:47 ` Steve French
2009-04-03 3:31 Steve French
2009-04-03 2:07 Stephen Rothwell
2009-02-24 6:56 Stephen Rothwell
2009-02-24 14:45 ` Steve French
2009-02-25 3:03 ` Stephen Rothwell
2008-12-02 2:23 Stephen Rothwell
2008-12-03 2:53 ` Stephen Rothwell
2008-12-03 3:19 ` David Miller
2008-12-03 11:57 ` Jeff Layton
2008-12-03 20:40 ` David Miller
2008-12-12 3:32 ` Stephen Rothwell
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=20090414114153.00467d45.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-cifs-client@lists$(echo .)samba.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=shirishp@us$(echo .)ibm.com \
--cc=smfrench@gmail$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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