From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Simona Vetter <simona.vetter@ffwll.ch>
Cc: Alice Ryhl <aliceryhl@google.com>,
Danilo Krummrich <dakr@kernel.org>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the drm-misc tree
Date: Fri, 9 Jan 2026 13:54:38 +1100 [thread overview]
Message-ID: <20260109135438.5b4f463d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
Hi all,
After merging the drm-misc tree, today's linux-next build (htmldocs)
produced this warning:
WARNING: drivers/gpu/drm/drm_gpuvm.c:1855 expecting prototype for drm_gpuvm_bo_obtain(). Prototype was for drm_gpuvm_bo_obtain_locked() instead
Introduced by commit
9bf4ca1e699c ("drm/gpuvm: drm_gpuvm_bo_obtain() requires lock and staged mode")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-01-09 2:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 2:54 Stephen Rothwell [this message]
2026-01-09 8:23 ` linux-next: build warning after merge of the drm-misc tree Alice Ryhl
-- strict thread matches above, loose matches on Subject: below --
2026-01-05 4:57 Stephen Rothwell
2025-12-16 1:00 Stephen Rothwell
2025-08-21 3:35 Stephen Rothwell
2025-07-16 10:31 Stephen Rothwell
2025-07-16 13:00 ` Andy Yan
2025-07-17 2:21 ` linux-next: " Randy Dunlap
2025-08-01 4:43 ` Stephen Rothwell
2025-08-01 6:28 ` Andy Yan
2025-08-01 10:30 ` Dmitry Baryshkov
2025-07-01 8:09 Stephen Rothwell
2025-07-01 8:51 ` Kandpal, Suraj
2025-06-18 5:03 Stephen Rothwell
2025-02-07 3:22 Stephen Rothwell
2024-11-08 6:56 Stephen Rothwell
2024-11-13 6:33 ` Stephen Rothwell
2024-10-09 6:26 Stephen Rothwell
2024-10-08 6:26 Stephen Rothwell
2024-10-03 3:21 Stephen Rothwell
2024-10-02 4:31 Stephen Rothwell
2024-10-02 4:28 Stephen Rothwell
2024-10-02 4:26 Stephen Rothwell
2024-10-02 4:22 Stephen Rothwell
2024-04-12 6:58 Stephen Rothwell
2024-04-12 7:01 ` Stephen Rothwell
2024-03-26 5:01 Stephen Rothwell
2019-10-10 23:45 Stephen Rothwell
2019-08-16 3:31 Stephen Rothwell
2019-08-16 4:48 ` Sam Ravnborg
2019-08-16 6:23 ` Daniel Vetter
2019-08-16 9:47 ` Laurent Pinchart
2019-08-16 12:24 ` Laurent Pinchart
2019-02-08 1:32 Stephen Rothwell
2019-02-08 9:29 ` Maxime Ripard
2019-01-07 23:58 Stephen Rothwell
2018-07-12 1:51 Stephen Rothwell
2017-04-05 0:41 Stephen Rothwell
2017-04-05 7:26 ` Neil Armstrong
2017-03-10 0:03 Stephen Rothwell
2016-11-22 1:45 Stephen Rothwell
2016-06-03 1:09 Stephen Rothwell
2015-09-23 3:20 Stephen Rothwell
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=20260109135438.5b4f463d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=simona.vetter@ffwll.ch \
/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