All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Daniel Vetter" <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm: avoid spurious EBUSY due to nonblocking atomic modesets (rev4)
Date: Fri, 06 Mar 2020 23:00:33 -0000	[thread overview]
Message-ID: <158353563367.3080.977878423138890416@emeril.freedesktop.org> (raw)
In-Reply-To: <20200225115024.2386811-1-daniel.vetter@ffwll.ch>

== Series Details ==

Series: drm: avoid spurious EBUSY due to nonblocking atomic modesets (rev4)
URL   : https://patchwork.freedesktop.org/series/45968/
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-06 23:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 11:50 [PATCH] drm: avoid spurious EBUSY due to nonblocking atomic modesets Daniel Vetter
2020-02-25 11:50 ` [Intel-gfx] " Daniel Vetter
2020-02-25 11:50 ` Daniel Vetter
2020-02-25 13:46 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: avoid spurious EBUSY due to nonblocking atomic modesets (rev3) Patchwork
2020-02-25 14:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-25 14:48 ` [Intel-gfx] [PATCH] drm: avoid spurious EBUSY due to nonblocking atomic modesets Ville Syrjälä
2020-02-25 14:48   ` Ville Syrjälä
2020-02-25 14:48   ` Ville Syrjälä
2020-02-25 15:09   ` Daniel Vetter
2020-02-25 15:09     ` Daniel Vetter
2020-02-25 15:09     ` Daniel Vetter
2020-02-25 15:34     ` Ville Syrjälä
2020-02-25 15:34       ` Ville Syrjälä
2020-02-25 15:34       ` Ville Syrjälä
2020-04-08 14:03       ` Ville Syrjälä
2020-04-08 14:03         ` Ville Syrjälä
2020-04-08 14:03         ` Ville Syrjälä
2020-04-08 15:34         ` Daniel Vetter
2020-04-08 15:34           ` Daniel Vetter
2020-04-08 15:34           ` Daniel Vetter
2020-03-06 22:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: avoid spurious EBUSY due to nonblocking atomic modesets (rev4) Patchwork
2020-03-06 23:00 ` Patchwork [this message]
2020-03-06 23:11 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-03-07  2:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: avoid spurious EBUSY due to nonblocking atomic modesets (rev5) Patchwork
2020-03-07  3:00 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2020-03-07  3:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=158353563367.3080.977878423138890416@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --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.