From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Casey Bowman" <casey.g.bowman@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.DOCS: warning for Splitting up platform-specific calls (rev2)
Date: Wed, 06 Apr 2022 00:45:46 -0000 [thread overview]
Message-ID: <164920594647.5450.12506012744404266033@emeril.freedesktop.org> (raw)
In-Reply-To: <20220331204343.1256150-1-casey.g.bowman@intel.com>
== Series Details ==
Series: Splitting up platform-specific calls (rev2)
URL : https://patchwork.freedesktop.org/series/102041/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/gem/i915_gem_context_types.h:417: warning: Function parameter or member 'client_link' not described in 'i915_gem_context'
next prev parent reply other threads:[~2022-04-06 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 20:43 [Intel-gfx] [PATCH v6 0/1] Splitting up platform-specific calls Casey Bowman
2022-03-31 20:43 ` [Intel-gfx] [PATCH v6 1/1] Split i915_run_as_guest into x86 and non-x86 Casey Bowman
2022-04-05 18:04 ` Casey Bowman
2022-04-05 20:06 ` Lucas De Marchi
2022-04-06 16:24 ` Lucas De Marchi
2022-03-31 22:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Splitting up platform-specific calls Patchwork
2022-03-31 23:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-06 0:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Splitting up platform-specific calls (rev2) Patchwork
2022-04-06 0:45 ` Patchwork [this message]
2022-04-06 1:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-06 6:21 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=164920594647.5450.12506012744404266033@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=casey.g.bowman@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.