From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Lyude Paul" <lyude@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915/dpcd_bl: Unbreak enable_dpcd_backlight modparam (rev2)
Date: Thu, 16 Apr 2020 17:15:47 -0000 [thread overview]
Message-ID: <158705734710.20886.16741532218467325413@emeril.freedesktop.org> (raw)
In-Reply-To: <20200413214407.1851002-1-lyude@redhat.com>
== Series Details ==
Series: drm/i915/dpcd_bl: Unbreak enable_dpcd_backlight modparam (rev2)
URL : https://patchwork.freedesktop.org/series/75895/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
/home/cidrm/kernel/Documentation/gpu/i915.rst:610: WARNING: duplicate label gpu/i915:layout, other instance in /home/cidrm/kernel/Documentation/gpu/i915.rst
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-16 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 21:44 [PATCH] drm/i915/dpcd_bl: Unbreak enable_dpcd_backlight modparam Lyude Paul
2020-04-13 21:44 ` [Intel-gfx] " Lyude Paul
2020-04-13 21:44 ` Lyude Paul
2020-04-14 22:27 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2020-04-14 22:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-04-16 17:15 ` Patchwork [this message]
2020-04-16 17:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dpcd_bl: Unbreak enable_dpcd_backlight modparam (rev2) Patchwork
2020-04-17 16:42 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-04-20 10:28 ` [PATCH] drm/i915/dpcd_bl: Unbreak enable_dpcd_backlight modparam Jani Nikula
2020-04-20 10:28 ` [Intel-gfx] " Jani Nikula
2020-04-20 10:28 ` Jani Nikula
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=158705734710.20886.16741532218467325413@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lyude@redhat.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.