From: Steve French <smfrench@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc1-mm2
Date: Fri, 18 Nov 2005 13:36:10 -0600 [thread overview]
Message-ID: <437E2D2A.2070308@austin.rr.com> (raw)
The missing XATTR ifdef is now fixed in cifs-2.6 git tree along with
some minor fixes related to mounts where sfu mount option specified.
Thanks for pointing this out.
Andy Whitcroft <apw@shadowen.org> wrote on 11/18/2005 05:29:47 AM:
> Andrew Morton wrote:
>
> > - cifs is busted when built as a module. Mysteriously.
>
> Don't know if this is related, but it appears that there is a problem
> linking it static. Specifically when you enable CONFIG_CIFS but not
> CONFIG_CIFS_XATTR. It seems that get_sfu_uid_mode() uses
> CIFSSMBQueryEA() which is only available when CIFS_XATTR is defined.
> Oddly the error seems to be reported against the function which follows:
>
> fs/built-in.o(.text+0x131520): In function `.cifs_get_inode_info':
> : undefined reference to `.CIFSSMBQueryEA'
> make: *** [.tmp_vmlinux1] Error 1
>
> -apw
next reply other threads:[~2005-11-18 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 19:36 Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-19 16:14 2.6.15-rc1-mm2 Stas Sergeev
2005-11-09 13:49 [PATCH 00/16] Adaptive read-ahead V7 Wu Fengguang
2005-11-09 13:49 ` [PATCH 05/16] readahead: some preparation Wu Fengguang
2005-11-18 7:46 ` 2.6.15-rc1-mm2 Andrew Morton
2005-11-18 8:56 ` 2.6.15-rc1-mm2 Benoit Boissinot
2005-11-18 9:04 ` 2.6.15-rc1-mm2 Andrew Morton
2005-11-18 9:13 ` 2.6.15-rc1-mm2 Benoit Boissinot
2005-11-18 13:43 ` 2.6.15-rc1-mm2 Rafael J. Wysocki
2005-11-18 10:10 ` 2.6.15-rc1-mm2 Mauro Carvalho Chehab
2005-11-18 10:55 ` 2.6.15-rc1-mm2 Wu Fengguang
2005-11-18 11:29 ` 2.6.15-rc1-mm2 Andy Whitcroft
2005-11-18 16:29 ` 2.6.15-rc1-mm2 Michael Krufky
2005-11-20 0:23 ` 2.6.15-rc1-mm2 Michal Piotrowski
2005-11-20 8:04 ` 2.6.15-rc1-mm2 Hugh Dickins
2005-11-20 12:53 ` 2.6.15-rc1-mm2 Michal Piotrowski
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=437E2D2A.2070308@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-kernel@vger.kernel.org \
/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