From: Steve French <smfrench@austin.rr.com>
To: niallain@gmail.com, Jeff Layton <jlayton@redhat.com>,
linux-next@vger.kernel.org, sfr@canb.auug.org.au,
linux-cifs-client@lists.samba.org
Subject: Re: linux-next: cifs tree build failure
Date: Thu, 02 Apr 2009 22:31:32 -0500 [thread overview]
Message-ID: <49D58314.5090306@austin.rr.com> (raw)
I added an ifdef to fs/cifs/connect.c which should address this.
next reply other threads:[~2009-04-03 3:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 3:31 Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 3:32 linux-next: cifs tree build failure Stephen Rothwell
2009-06-15 10:46 ` Jeff Layton
2009-06-15 13:47 ` Steve French
2009-04-14 1:41 Stephen Rothwell
2009-04-15 2:59 ` Stephen Rothwell
2009-04-15 3:10 ` Steve French
2009-04-15 3:20 ` Stephen Rothwell
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=49D58314.5090306@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-next@vger.kernel.org \
--cc=niallain@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).