From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [axboe:rw_iter 453/525] drivers/gpu/drm/adp/adp_drv.c:85:3: error: field designator 'read' does not refer to any field in type 'const struct file_operations'
Date: Thu, 26 Mar 2026 16:10:35 +0800 [thread overview]
Message-ID: <202603261655.R6thuPg9-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git rw_iter
head: d5f290ca006c2bdabff8aa383fd3cf9cf9194259
commit: 6227c44455927ebea005dbc4b69c4ba8fc4a4089 [453/525] fs: finally remove ->read() and ->write() from file_operations
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260326/202603261655.R6thuPg9-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260326/202603261655.R6thuPg9-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/202603261655.R6thuPg9-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/adp/adp_drv.c:85:3: error: field designator 'read' does not refer to any field in type 'const struct file_operations'
85 | .read = drm_read,
| ~^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +85 drivers/gpu/drm/adp/adp_drv.c
332122eba628d5 Sasha Finkelstein 2025-02-24 77
332122eba628d5 Sasha Finkelstein 2025-02-24 78 static const struct file_operations adp_fops = {
332122eba628d5 Sasha Finkelstein 2025-02-24 79 .owner = THIS_MODULE,
332122eba628d5 Sasha Finkelstein 2025-02-24 80 .open = adp_open,
332122eba628d5 Sasha Finkelstein 2025-02-24 81 .release = drm_release,
332122eba628d5 Sasha Finkelstein 2025-02-24 82 .unlocked_ioctl = drm_ioctl,
332122eba628d5 Sasha Finkelstein 2025-02-24 83 .compat_ioctl = drm_compat_ioctl,
332122eba628d5 Sasha Finkelstein 2025-02-24 84 .poll = drm_poll,
afd750c9e3e8ed Jens Axboe 2026-03-04 @85 .read = drm_read,
332122eba628d5 Sasha Finkelstein 2025-02-24 86 .llseek = noop_llseek,
332122eba628d5 Sasha Finkelstein 2025-02-24 87 .mmap = drm_gem_mmap,
332122eba628d5 Sasha Finkelstein 2025-02-24 88 .fop_flags = FOP_UNSIGNED_OFFSET,
332122eba628d5 Sasha Finkelstein 2025-02-24 89 DRM_GEM_DMA_UNMAPPED_AREA_FOPS
332122eba628d5 Sasha Finkelstein 2025-02-24 90 };
332122eba628d5 Sasha Finkelstein 2025-02-24 91
:::::: The code at line 85 was first introduced by commit
:::::: afd750c9e3e8ed7975f551be58d3bd50766d8d7c drm: convert remaining fops to read/write iterators
:::::: TO: Jens Axboe <axboe@kernel.dk>
:::::: CC: Jens Axboe <axboe@kernel.dk>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-26 8:11 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=202603261655.R6thuPg9-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--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