From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [RFC PATCH] drm: Add support for io_uring's uring_cmd in DRM/accel
Date: Sun, 8 Jun 2025 03:34:28 +0800 [thread overview]
Message-ID: <202506080322.Lsc4bCGT-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250606180806.2193463-1-zachary.mckevitt@oss.qualcomm.com>
References: <20250606180806.2193463-1-zachary.mckevitt@oss.qualcomm.com>
TO: Zack McKevitt <zachary.mckevitt@oss.qualcomm.com>
Hi Zack,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-exynos/exynos-drm-next]
[also build test WARNING 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
:::::: branch date: 25 hours ago
:::::: commit date: 25 hours ago
config: x86_64-randconfig-161-20250607 (https://download.01.org/0day-ci/archive/20250608/202506080322.Lsc4bCGT-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202506080322.Lsc4bCGT-lkp@intel.com/
smatch warnings:
drivers/gpu/drm/drm_ioctl.c:958 drm_uring_cmd() warn: statement has no effect 'const'
vim +/const +958 drivers/gpu/drm/drm_ioctl.c
09504f8ef576ed Zack McKevitt 2025-06-06 940
09504f8ef576ed Zack McKevitt 2025-06-06 941 /**
09504f8ef576ed Zack McKevitt 2025-06-06 942 * drm_uring_cmd - Implement uring_cmd callback for io_uring
09504f8ef576ed Zack McKevitt 2025-06-06 943 * @cmd: pointer to io_uring_cmd struct
09504f8ef576ed Zack McKevitt 2025-06-06 944 * @issue_flags: flags specified by io_uring's issue implementation
09504f8ef576ed Zack McKevitt 2025-06-06 945 *
09504f8ef576ed Zack McKevitt 2025-06-06 946 * This function implements the uring_cmd file operation to incorporate
09504f8ef576ed Zack McKevitt 2025-06-06 947 * arbitrary io_uring functionality for drm. Currently, it acts as a way
09504f8ef576ed Zack McKevitt 2025-06-06 948 * for io_uring to issue ioctls to a drm device, so this function
09504f8ef576ed Zack McKevitt 2025-06-06 949 * dispatches ioctls to the standard drm ioctl interface.
09504f8ef576ed Zack McKevitt 2025-06-06 950 *
09504f8ef576ed Zack McKevitt 2025-06-06 951 * Returns:
09504f8ef576ed Zack McKevitt 2025-06-06 952 * Zero on success, negative error code on failure.
09504f8ef576ed Zack McKevitt 2025-06-06 953 */
09504f8ef576ed Zack McKevitt 2025-06-06 954 int drm_uring_cmd(struct io_uring_cmd *cmd, unsigned int issue_flags)
09504f8ef576ed Zack McKevitt 2025-06-06 955 {
09504f8ef576ed Zack McKevitt 2025-06-06 956 switch (cmd->cmd_op) {
09504f8ef576ed Zack McKevitt 2025-06-06 957 case DRM_URING_CMD_IOCTL:
09504f8ef576ed Zack McKevitt 2025-06-06 @958 const struct drm_uring_cmd_ioctl *drm_cmd = io_uring_sqe_cmd(cmd->sqe);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-06-07 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 19:34 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=202506080322.Lsc4bCGT-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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.