All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zack McKevitt <zachary.mckevitt@oss.qualcomm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] drm: Add support for io_uring's uring_cmd in DRM/accel
Date: Sat, 7 Jun 2025 14:18:23 +0800	[thread overview]
Message-ID: <202506071421.2BsXneKu-lkp@intel.com> (raw)
In-Reply-To: <20250606180806.2193463-1-zachary.mckevitt@oss.qualcomm.com>

Hi Zack,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on drm-exynos/exynos-drm-next]
[also build test ERROR on linus/master v6.15 next-20250606]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Zack-McKevitt/drm-Add-support-for-io_uring-s-uring_cmd-in-DRM-accel/20250607-021118
base:   https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next
patch link:    https://lore.kernel.org/r/20250606180806.2193463-1-zachary.mckevitt%40oss.qualcomm.com
patch subject: [RFC PATCH] drm: Add support for io_uring's uring_cmd in DRM/accel
config: riscv-randconfig-002-20250607 (https://download.01.org/0day-ci/archive/20250607/202506071421.2BsXneKu-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250607/202506071421.2BsXneKu-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/202506071421.2BsXneKu-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/drm_ioctl.c:958:3: error: expected expression
                   const struct drm_uring_cmd_ioctl *drm_cmd = io_uring_sqe_cmd(cmd->sqe);
                   ^
>> drivers/gpu/drm/drm_ioctl.c:959:28: error: use of undeclared identifier 'drm_cmd'
                   unsigned int ioctl_cmd = drm_cmd->ioctl_cmd;
                                            ^
   drivers/gpu/drm/drm_ioctl.c:960:29: error: use of undeclared identifier 'drm_cmd'
                   unsigned long ioctl_arg = drm_cmd->arg;
                                             ^
   3 errors generated.


vim +958 drivers/gpu/drm/drm_ioctl.c

   940	
   941	/**
   942	 * drm_uring_cmd - Implement uring_cmd callback for io_uring
   943	 * @cmd: pointer to io_uring_cmd struct
   944	 * @issue_flags: flags specified by io_uring's issue implementation
   945	 *
   946	 * This function implements the uring_cmd file operation to incorporate
   947	 * arbitrary io_uring functionality for drm. Currently, it acts as a way
   948	 * for io_uring to issue ioctls to a drm device, so this function
   949	 * dispatches ioctls to the standard drm ioctl interface.
   950	 *
   951	 * Returns:
   952	 * Zero on success, negative error code on failure.
   953	 */
   954	int drm_uring_cmd(struct io_uring_cmd *cmd, unsigned int issue_flags)
   955	{
   956		switch (cmd->cmd_op) {
   957		case DRM_URING_CMD_IOCTL:
 > 958			const struct drm_uring_cmd_ioctl *drm_cmd = io_uring_sqe_cmd(cmd->sqe);
 > 959			unsigned int ioctl_cmd = drm_cmd->ioctl_cmd;

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-06-07  6:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06 18:08 [RFC PATCH] drm: Add support for io_uring's uring_cmd in DRM/accel Zack McKevitt
2025-06-07  3:52 ` kernel test robot
2025-06-07  6:18 ` kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-07 19:34 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=202506071421.2BsXneKu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=zachary.mckevitt@oss.qualcomm.com \
    /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.