From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Lionel Landwerlin" <lionel.g.landwerlin@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [v4,1/3] drm/i915/perf: remove generated code
Date: Fri, 06 Mar 2020 16:51:01 -0000 [thread overview]
Message-ID: <158351346173.3083.17759141330686064536@emeril.freedesktop.org> (raw)
In-Reply-To: <20200306100557.2077450-1-lionel.g.landwerlin@intel.com>
== Series Details ==
Series: series starting with [v4,1/3] drm/i915/perf: remove generated code
URL : https://patchwork.freedesktop.org/series/74379/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/display/intel_dpll_mgr.h:285: warning: Function parameter or member 'get_freq' not described in 'intel_shared_dpll_funcs'
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-06 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 10:05 [Intel-gfx] [PATCH v4 1/3] drm/i915/perf: remove generated code Lionel Landwerlin
2020-03-06 10:05 ` [Intel-gfx] [PATCH v4 2/3] drm/i915/perf: remove redundant power configuration register override Lionel Landwerlin
2020-03-12 17:46 ` Tvrtko Ursulin
2020-03-06 10:05 ` [Intel-gfx] [PATCH v4 3/3] drm/i915/perf: introduce global sseu pinning Lionel Landwerlin
2020-03-12 18:19 ` Tvrtko Ursulin
2020-03-12 22:41 ` Tvrtko Ursulin
2020-03-13 13:40 ` Lionel Landwerlin
2020-03-13 13:34 ` Lionel Landwerlin
2020-03-06 16:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v4,1/3] drm/i915/perf: remove generated code Patchwork
2020-03-06 16:51 ` Patchwork [this message]
2020-03-06 17:19 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-03-12 13:51 ` [Intel-gfx] [PATCH v4 1/3] " Dan Carpenter
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=158351346173.3083.17759141330686064536@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).