From: kernel test robot <lkp@intel.com>
To: NeilBrown <neil@brown.name>
Cc: oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>,
Christian Brauner <brauner@kernel.org>
Subject: [brauner-github:vfs-7.3.misc 9/9] Warning: fs/gfs2/inode.c:972 Excess function parameter 'excl' description in 'gfs2_create'
Date: Thu, 02 Jul 2026 11:30:57 +0800 [thread overview]
Message-ID: <202607021108.ZTNE6DAq-lkp@intel.com> (raw)
tree: https://github.com/brauner/linux.git vfs-7.3.misc
head: cfbd57798c634d544659b4f1329b3765e04af5ab
commit: cfbd57798c634d544659b4f1329b3765e04af5ab [9/9] Remove excl arg to ->create inode_operation
config: loongarch-randconfig-r073-20260702 (https://download.01.org/0day-ci/archive/20260702/202607021108.ZTNE6DAq-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.3.0
smatch: v0.5.0-9185-gbcc58b9c
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260702/202607021108.ZTNE6DAq-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/202607021108.ZTNE6DAq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/gfs2/inode.c:972 Excess function parameter 'excl' description in 'gfs2_create'
>> Warning: fs/gfs2/inode.c:972 Excess function parameter 'excl' description in 'gfs2_create'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-02 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 3:30 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-01 19:32 [brauner-github:vfs-7.3.misc 9/9] Warning: fs/gfs2/inode.c:972 Excess function parameter 'excl' description in 'gfs2_create' kernel test robot
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=202607021108.ZTNE6DAq-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=neil@brown.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.