From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Imre Deak" <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915: Fix the GT fence revocation runtime PM logic
Date: Mon, 22 Mar 2021 23:25:18 -0000 [thread overview]
Message-ID: <161645551870.19228.6783705267644780316@emeril.freedesktop.org> (raw)
In-Reply-To: <20210322204223.919936-1-imre.deak@intel.com>
== Series Details ==
Series: drm/i915: Fix the GT fence revocation runtime PM logic
URL : https://patchwork.freedesktop.org/series/88300/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/intel_runtime_pm.c:430: warning: expecting prototype for intel_runtime_pm_get_if_in_use(). Prototype was for __intel_runtime_pm_get_if_active() instead
./drivers/gpu/drm/i915/intel_runtime_pm.c:430: warning: Function parameter or member 'ignore_usecount' not described in '__intel_runtime_pm_get_if_active'
./drivers/gpu/drm/i915/intel_runtime_pm.c:430: warning: expecting prototype for intel_runtime_pm_get_if_in_use(). Prototype was for __intel_runtime_pm_get_if_active() instead
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-22 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 20:42 [Intel-gfx] [PATCH] drm/i915: Fix the GT fence revocation runtime PM logic Imre Deak
2021-03-22 23:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-03-22 23:25 ` Patchwork [this message]
2021-03-22 23:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-03-23 21:29 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-03-24 5:43 ` Imre Deak
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=161645551870.19228.6783705267644780316@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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.