public inbox for [email protected]
 help / color / mirror / Atom feed
From: Stephen Rothwell <[email protected]>
To: Steve French <[email protected]>
Cc: CIFS <[email protected]>,
	Enzo Matsumiya <[email protected]>,
	Linux Kernel Mailing List <[email protected]>,
	Linux Next Mailing List <[email protected]>
Subject: linux-next: build warning after merge of the cifs tree
Date: Mon, 23 May 2022 10:57:36 +1000	[thread overview]
Message-ID: <[email protected]> (raw)

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2022-05-23  0:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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