From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Simona Vetter <simona.vetter@ffwll•ch>,
Jani Nikula <jani.nikula@linux•intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux•intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel•com>
Cc: 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-intel tree
Date: Tue, 1 Oct 2024 13:43:31 +1000 [thread overview]
Message-ID: <20241001134331.7b4d4ca5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
Hi all,
After merging the drm-intel tree, today's linux-next build (htmldocs)
produced this warning:
drivers/gpu/drm/i915/i915_irq.c:1: warning: 'intel_runtime_pm_disable_interrupts' not found
drivers/gpu/drm/i915/i915_irq.c:1: warning: 'intel_runtime_pm_enable_interrupts' not found
Introduced by commit
3de5774cb8c0 ("drm/i915/irq: Rename suspend/resume functions")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-10-01 3:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 3:43 Stephen Rothwell [this message]
2024-10-11 5:57 ` linux-next: build warning after merge of the drm-intel tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-06-12 4:11 Stephen Rothwell
2024-07-14 23:12 ` Stephen Rothwell
2024-07-15 4:21 ` Golani, Mitulkumar Ajitkumar
2024-07-15 12:13 ` Maarten Lankhorst
2024-07-30 10:10 ` Stephen Rothwell
2024-04-18 6:38 Stephen Rothwell
2024-02-19 5:17 Stephen Rothwell
2023-11-14 3:17 Stephen Rothwell
2023-11-14 8:22 ` Jani Nikula
2023-11-14 8:53 ` Jani Nikula
2024-01-21 22:25 ` Stephen Rothwell
2024-01-22 17:22 ` Jani Nikula
2022-11-30 3:45 Stephen Rothwell
2015-05-07 5:29 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=20241001134331.7b4d4ca5@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=jani.nikula@linux$(echo .)intel.com \
--cc=joonas.lahtinen@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rodrigo.vivi@intel$(echo .)com \
--cc=simona.vetter@ffwll$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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