From: Steve French <smfrench@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: CIFS <linux-cifs@vger.kernel.org>,
Enzo Matsumiya <ematsumiya@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the cifs tree
Date: Sun, 22 May 2022 21:29:52 -0500 [thread overview]
Message-ID: <CAH2r5msr=g=6-cSmmeTXm5x1zrdaeRykow7B=EL30PaRnTm4Jw@mail.gmail.com> (raw)
In-Reply-To: <20220523105736.1f42b837@canb.auug.org.au>
Added trivial patch to cifs-2.6.git for-next to fix the warning
On Sun, May 22, 2022 at 7:57 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the cifs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/cifs/connect.c: In function 'is_path_remote':
> fs/cifs/connect.c:3436:14: warning: unused variable 'nodfs' [-Wunused-variable]
> 3436 | bool nodfs = cifs_sb->mnt_cifs_flags & CIFS_MOUNT_NO_DFS;
> | ^~~~~
>
> Introduced by commit
>
> 421ef3d56513 ("cifs: don't call cifs_dfs_query_info_nonascii_quirk() if nodfs was set")
>
> --
> Cheers,
> Stephen Rothwell
--
Thanks,
Steve
next prev parent reply other threads:[~2022-05-23 2:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 0:57 linux-next: build warning after merge of the cifs tree Stephen Rothwell
2022-05-23 2:29 ` Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 1:47 Stephen Rothwell
2024-01-19 3:02 ` Steve French
2021-02-04 22:51 Stephen Rothwell
2019-07-18 23:16 Stephen Rothwell
2019-07-18 23:38 ` 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
2017-11-20 23:19 Stephen Rothwell
[not found] ` <20171121101916.4970d5f9-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2017-11-20 23:37 ` Steve French
2017-06-26 0:07 Stephen Rothwell
[not found] ` <20170626100728.0494601c-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2017-06-26 16:57 ` 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
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:25 Stephen Rothwell
2011-01-21 1:05 Stephen Rothwell
2011-01-21 1:20 ` 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
2010-09-24 3:48 Stephen Rothwell
2010-09-24 11:13 ` Jeff Layton
2010-08-26 1:02 Stephen Rothwell
[not found] ` <20100826110229.931ab5bf.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-08-26 2:07 ` 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='CAH2r5msr=g=6-cSmmeTXm5x1zrdaeRykow7B=EL30PaRnTm4Jw@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=ematsumiya@suse.de \
--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).