From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jlayton:nfsd-tracepoints 8/9] fs/nfsd/nfs4proc.c:797:2: warning: label at end of compound statement is a C2x extension
Date: Sun, 9 Mar 2025 20:19:24 +0800 [thread overview]
Message-ID: <202503092055.5Awz8EoC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git nfsd-tracepoints
head: 7162c90c3e04a073c111a5821e529377ce2ab43f
commit: f1681c62918a99afaf3528b5332aa647740eb818 [8/9] nfsd: add tracepoints around nfsd_create events
config: powerpc-allyesconfig (https://download.01.org/0day-ci/archive/20250309/202503092055.5Awz8EoC-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250309/202503092055.5Awz8EoC-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503092055.5Awz8EoC-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/nfsd/nfs4proc.c:797:2: warning: label at end of compound statement is a C2x extension [-Wc2x-extensions]
}
^
1 warning generated.
vim +797 fs/nfsd/nfs4proc.c
778
779 static umode_t nfs_type_to_vfs_type(enum nfs_ftype4 nfstype)
780 {
781 switch (nfstype) {
782 case NF4REG:
783 return S_IFREG;
784 case NF4DIR:
785 return S_IFDIR;
786 case NF4BLK:
787 return S_IFBLK;
788 case NF4CHR:
789 return S_IFCHR;
790 case NF4LNK:
791 return S_IFLNK;
792 case NF4SOCK:
793 return S_IFSOCK;
794 case NF4FIFO:
795 return S_IFIFO;
796 default:
> 797 }
798 return 0;
799 }
800
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-09 12:20 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 \
--in-reply-to=202503092055.5Awz8EoC-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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