From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>
Subject: [brauner-vfs:b4/vfs-bdev-file 31/35] block/fops.c:866:56: error: initializer element is not a compile-time constant
Date: Wed, 24 Jan 2024 10:16:12 +0800 [thread overview]
Message-ID: <202401241034.sSm707gY-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git b4/vfs-bdev-file
head: 86d0fab9651f2edb5dc7094c36ce414bf2c407ff
commit: d200dd4d01b253bf3964c013247dfea89baef880 [31/35] block: use file->f_op to indicate restricted writes
config: arm-randconfig-001-20240124 (https://download.01.org/0day-ci/archive/20240124/202401241034.sSm707gY-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240124/202401241034.sSm707gY-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/202401241034.sSm707gY-lkp@intel.com/
All errors (new ones prefixed by >>):
>> block/fops.c:866:56: error: initializer element is not a compile-time constant
const struct file_operations def_blk_fops_restricted = def_blk_fops;
^~~~~~~~~~~~
1 error generated.
vim +866 block/fops.c
864
865 /* Indicator that this block device is opened with restricted write access. */
> 866 const struct file_operations def_blk_fops_restricted = def_blk_fops;
867
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-24 2:16 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=202401241034.sSm707gY-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).