From: kernel test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-unionfs@vger.kernel.org
Subject: [mszeredi-vfs:statmount-v3 3/4] <stdin>:1573:2: warning: syscall statmount not implemented
Date: Sun, 1 Oct 2023 00:33:26 +0800 [thread overview]
Message-ID: <202310010048.tqG9YpMs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git statmount-v3
head: 5321994510f383b43dd2d49fcbdaedcf8cba1306
commit: 752065afadf4dbffa79febfc8e30d771353c1584 [3/4] add statmount(2) syscall
config: mips-ath25_defconfig (https://download.01.org/0day-ci/archive/20231001/202310010048.tqG9YpMs-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231001/202310010048.tqG9YpMs-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/202310010048.tqG9YpMs-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> <stdin>:1573:2: warning: syscall statmount not implemented [-W#warnings]
1573 | #warning syscall statmount not implemented
| ^
1 warning generated.
--
>> <stdin>:1573:2: warning: syscall statmount not implemented [-W#warnings]
1573 | #warning syscall statmount not implemented
| ^
1 warning generated.
--
>> <stdin>:1573:2: warning: syscall statmount not implemented [-W#warnings]
1573 | #warning syscall statmount not implemented
| ^
1 warning generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-30 16:33 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=202310010048.tqG9YpMs-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mszeredi@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).