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: Add a DP1.2 compatible way to read LTTPR capabilities (rev2)
Date: Tue, 22 Mar 2022 14:55:55 -0000 [thread overview]
Message-ID: <164796095585.20007.3473001448465398508@emeril.freedesktop.org> (raw)
In-Reply-To: <20220228201234.1448613-1-imre.deak@intel.com>
== Series Details ==
Series: drm/i915: Add a DP1.2 compatible way to read LTTPR capabilities (rev2)
URL : https://patchwork.freedesktop.org/series/100851/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/display/intel_drrs.c:1: warning: 'intel_drrs_enable' not found
./drivers/gpu/drm/i915/display/intel_drrs.c:1: warning: 'intel_drrs_disable' not found
next prev parent reply other threads:[~2022-03-22 14:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 20:12 [PATCH] drm/i915: Add a DP1.2 compatible way to read LTTPR capabilities Imre Deak
2022-02-28 20:12 ` [Intel-gfx] " Imre Deak
2022-03-01 0:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-03-01 1:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-01 14:14 ` [PATCH] " Ville Syrjälä
2022-03-01 14:14 ` [Intel-gfx] " Ville Syrjälä
2022-03-01 18:14 ` Imre Deak
2022-03-01 18:14 ` [Intel-gfx] " Imre Deak
2022-03-01 18:24 ` Ville Syrjälä
2022-03-01 18:24 ` [Intel-gfx] " Ville Syrjälä
2022-03-22 14:38 ` [PATCH v2] " Imre Deak
2022-03-22 14:38 ` [Intel-gfx] " Imre Deak
2022-03-22 17:31 ` Ville Syrjälä
2022-03-22 17:31 ` [Intel-gfx] " Ville Syrjälä
2022-03-22 14:48 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add a DP1.2 compatible way to read LTTPR capabilities (rev2) Patchwork
2022-03-22 14:55 ` Patchwork [this message]
2022-03-22 15:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-22 21:50 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=164796095585.20007.3473001448465398508@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.