From: kernel test robot <lkp@intel.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
Danilo Krummrich <dakr@kernel.org>,
Boris Brezillon <bbrezillon@kernel.org>
Subject: [drm-misc:for-linux-next 1/2] Warning: drivers/gpu/drm/drm_gpuvm.c:1836 expecting prototype for drm_gpuvm_bo_obtain(). Prototype was for drm_gpuvm_bo_obtain_locked() instead
Date: Fri, 09 Jan 2026 12:00:36 +0800 [thread overview]
Message-ID: <202601091113.0b0WuRML-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/misc/kernel.git for-linux-next
head: ec27500c8f2b65a3be6ce39a5844d6d246d1b2b0
commit: 9bf4ca1e699c272defe9636f9812ff33a448d650 [1/2] drm/gpuvm: drm_gpuvm_bo_obtain() requires lock and staged mode
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260109/202601091113.0b0WuRML-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260109/202601091113.0b0WuRML-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/202601091113.0b0WuRML-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/gpu/drm/drm_gpuvm.c:1836 expecting prototype for drm_gpuvm_bo_obtain(). Prototype was for drm_gpuvm_bo_obtain_locked() instead
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-09 4:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 4:00 kernel test robot [this message]
2026-01-09 8:20 ` [PATCH] drm/gpuvm: fix name in kernel doc of drm_gpuvm_bo_obtain_locked() Alice Ryhl
2026-01-09 16:22 ` Danilo Krummrich
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=202601091113.0b0WuRML-lkp@intel.com \
--to=lkp@intel.com \
--cc=aliceryhl@google.com \
--cc=bbrezillon@kernel.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--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.