All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Umesh Nerlige Ramappa" <umesh.nerlige.ramappa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.DOCS: warning for Enable triggered perf query for Xe_HP
Date: Tue, 03 Aug 2021 21:17:11 -0000	[thread overview]
Message-ID: <162802543154.9815.10583705039109109818@emeril.freedesktop.org> (raw)
In-Reply-To: <20210803201349.31031-1-umesh.nerlige.ramappa@intel.com>

== Series Details ==

Series: Enable triggered perf query for Xe_HP
URL   : https://patchwork.freedesktop.org/series/93357/
State : warning

== Summary ==

$ make htmldocs 2>&1 > /dev/null | grep i915
./include/uapi/drm/i915_drm.h:2408: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
./include/uapi/drm/i915_drm.h:2408: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
./include/uapi/drm/i915_drm.h:2408: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
./include/uapi/drm/i915_drm.h:2408: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst



  parent reply	other threads:[~2021-08-03 21:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 20:13 [PATCH 0/8] Enable triggered perf query for Xe_HP Umesh Nerlige Ramappa
2021-08-03 20:13 ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:13 ` [PATCH 1/8] drm/i915/gt: Lock intel_engine_apply_whitelist with uncore->lock Umesh Nerlige Ramappa
2021-08-03 20:13   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:13 ` [PATCH 2/8] drm/i915/gt: Refactor _wa_add to reuse wa_index and wa_list_grow Umesh Nerlige Ramappa
2021-08-03 20:13   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:13 ` [PATCH 3/8] drm/i915/gt: Check for conflicting RING_NONPRIV Umesh Nerlige Ramappa
2021-08-03 20:13   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:13 ` [PATCH 4/8] drm/i915/gt: Enable dynamic adjustment of RING_NONPRIV Umesh Nerlige Ramappa
2021-08-03 20:13   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:13 ` [PATCH 5/8] drm/i915/perf: Ensure observation logic is not clock gated Umesh Nerlige Ramappa
2021-08-03 20:13   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:13 ` [PATCH 6/8] drm/i915/perf: Whitelist OA report trigger registers Umesh Nerlige Ramappa
2021-08-03 20:13   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:13 ` [PATCH 7/8] drm/i915/perf: Whitelist OA counter and buffer registers Umesh Nerlige Ramappa
2021-08-03 20:13   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:13 ` [PATCH 8/8] drm/i915/perf: Map OA buffer to user space for gen12 performance query Umesh Nerlige Ramappa
2021-08-03 20:13   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:18 ` [PATCH 0/8] Enable triggered perf query for Xe_HP Umesh Nerlige Ramappa
2021-08-03 20:18   ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 20:27   ` Umesh Nerlige Ramappa
2021-08-03 20:27     ` [Intel-gfx] " Umesh Nerlige Ramappa
2021-08-03 21:17 ` Patchwork [this message]
2021-08-03 21:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " 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=162802543154.9815.10583705039109109818@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=umesh.nerlige.ramappa@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 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.