All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matt Roper" <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915/ehl: Check PHY type before reading DPLL frequency (rev2)
Date: Tue, 03 Mar 2020 20:33:30 -0000	[thread overview]
Message-ID: <158326761026.15377.4074723959374989921@emeril.freedesktop.org> (raw)
In-Reply-To: <20200303182904.952445-1-matthew.d.roper@intel.com>

== Series Details ==

Series: drm/i915/ehl: Check PHY type before reading DPLL frequency (rev2)
URL   : https://patchwork.freedesktop.org/series/74214/
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

  parent reply	other threads:[~2020-03-03 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 18:29 [Intel-gfx] [PATCH] drm/i915/ehl: Check PHY type before reading DPLL frequency Matt Roper
2020-03-03 18:34 ` Matt Roper
2020-03-03 18:50   ` Imre Deak
2020-03-03 19:06     ` Imre Deak
2020-03-03 19:50       ` [Intel-gfx] [PATCH v2] " Matt Roper
2020-03-03 20:04 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2020-03-03 20:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-03 20:33 ` Patchwork [this message]
2020-03-03 20:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/ehl: Check PHY type before reading DPLL frequency (rev2) Patchwork
2020-03-04  9:55 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-03-04 14:03   ` Matt Roper

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=158326761026.15377.4074723959374989921@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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.