linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-cifs@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jeff Layton <jlayton@redhat.com>
Subject: Re: linux-next: build failure after merge of the cifs tree
Date: Wed, 18 Jan 2012 18:31:11 -0600	[thread overview]
Message-ID: <CAH2r5mv-dbFM0jf9V+=y-N8tuQey=MgcfToPzBg3hRvFbCWeBA@mail.gmail.com> (raw)
In-Reply-To: <20120119110153.7ffa3312b2943386750ac7ed@canb.auug.org.au>

I already fixed that and merged it into cifs-2.6.git.   If you repull
you will get the fix for that.

On Wed, Jan 18, 2012 at 6:01 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 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_set_vol_auth':
> fs/cifs/connect.c:3843:17: error: 'CIFSSEC_MUST_LANMAN' undeclared (first use in this function)
> fs/cifs/connect.c:3843:17: note: each undeclared identifier is reported only once for each function it appears in
>
> Caused by commit 8a8798a5ff90 ("cifs: fetch credentials out of keyring
> for non-krb5 auth multiuser mounts").
>
> I have used the cifs tree from next-20120118 for today.
> --
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/



-- 
Thanks,

Steve

  reply	other threads:[~2012-01-19  0:31 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19  0:01 linux-next: build failure after merge of the cifs tree Stephen Rothwell
2012-01-19  0:31 ` Steve French [this message]
  -- 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
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
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='CAH2r5mv-dbFM0jf9V+=y-N8tuQey=MgcfToPzBg3hRvFbCWeBA@mail.gmail.com' \
    --to=smfrench@gmail.com \
    --cc=jlayton@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).