From: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Shirish Pargaonkar
<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: linux-next: build warning after merge of the cifs tree
Date: Wed, 25 Aug 2010 21:07:08 -0500 [thread overview]
Message-ID: <AANLkTikvKchHEFR_F-Fdo6Z8n2XKbi4tRh0eYnjzVQJ9@mail.gmail.com> (raw)
In-Reply-To: <20100826110229.931ab5bf.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
On Wed, Aug 25, 2010 at 8:02 PM, Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org> wrote:
> Hi all,
>
> After merging the cifs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/cifs/sess.c: In function 'CIFS_SessSetup':
> fs/cifs/sess.c:623: warning: unused variable 'ntlmsspblob'
>
> Introduced by commit 9fbc590860e75785bdaf8b83e48fabfe4d4f7d58 ("[CIFS]
> Fix ntlmv2 auth with ntlmssp").
Shirish's patch doesn't use that local variable when experimental is
off - I will talk to him about simply moving the local variable to
eliminate the unused variable warning.
--
Thanks,
Steve
next prev parent reply other threads:[~2010-08-26 2:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 1:02 linux-next: build warning after merge of the cifs tree Stephen Rothwell
[not found] ` <20100826110229.931ab5bf.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-08-26 2:07 ` Steve French [this message]
2010-09-24 3:48 Stephen Rothwell
2010-09-24 11:13 ` Jeff Layton
2010-09-24 3:55 Stephen Rothwell
[not found] ` <20100924135531.96e5ac72.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-10-19 5:21 ` Stephen Rothwell
2010-10-19 13:13 ` Jeff Layton
[not found] ` <20101019091339.38e45faa-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-10-19 15:48 ` Shirish Pargaonkar
2011-01-21 1:05 Stephen Rothwell
2011-01-21 1:20 ` Jeff Layton
2011-01-31 2:25 Stephen Rothwell
2011-01-31 2:27 Stephen Rothwell
[not found] ` <20110131132743.4ae5d4ae.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2011-01-31 3:25 ` Steve French
2011-01-31 2:30 Stephen Rothwell
2011-01-31 10:49 ` Suresh Jayaraman
[not found] ` <4D4693CF.9090903-l3A5Bk7waGM@public.gmane.org>
2011-01-31 11:38 ` Pavel Shilovsky
2011-01-31 12:29 ` Jeff Layton
2017-06-26 0:07 Stephen Rothwell
[not found] ` <20170626100728.0494601c-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2017-06-26 16:57 ` Steve French
2017-11-20 23:19 Stephen Rothwell
[not found] ` <20171121101916.4970d5f9-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2017-11-20 23:37 ` Steve French
2018-01-03 22:33 Stephen Rothwell
2018-01-03 22:44 ` Steve French
[not found] ` <CAH2r5mvgtC3Y_aLxk7-_R8E=ohR1LoFSkiqZZ6rhn9azXY05xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-04 5:52 ` Stephen Rothwell
2019-07-18 23:16 Stephen Rothwell
2019-07-18 23:38 ` Steve French
2021-02-04 22:51 Stephen Rothwell
2022-05-23 0:57 Stephen Rothwell
2022-05-23 2:29 ` Steve French
2024-01-19 1:47 Stephen Rothwell
2024-01-19 3:02 ` 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=AANLkTikvKchHEFR_F-Fdo6Z8n2XKbi4tRh0eYnjzVQJ9@mail.gmail.com \
--to=smfrench-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org \
--cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).