From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Lyude Paul" <lyude@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: kernel-doc fixes for new DP helpers
Date: Tue, 22 Sep 2020 18:52:05 -0000 [thread overview]
Message-ID: <160080072584.13390.8098876479043768411@emeril.freedesktop.org> (raw)
In-Reply-To: <20200922175357.42998-1-lyude@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 611 bytes --]
== Series Details ==
Series: drm/i915: kernel-doc fixes for new DP helpers
URL : https://patchwork.freedesktop.org/series/81985/
State : failure
== Summary ==
Applying: drm/dp: fix kernel-doc warnings at drm_dp_helper.c
Using index info to reconstruct a base tree...
M drivers/gpu/drm/drm_dp_helper.c
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.
Applying: drm/dp: fix a kernel-doc issue at drm_edid.c
Using index info to reconstruct a base tree...
M drivers/gpu/drm/drm_edid.c
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.
[-- Attachment #1.2: Type: text/html, Size: 1137 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-09-22 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 17:53 [Intel-gfx] [RESEND PATCH 0/2] drm/i915: kernel-doc fixes for new DP helpers Lyude Paul
2020-09-22 17:53 ` [RESEND PATCH 1/2] drm/dp: fix kernel-doc warnings at drm_dp_helper.c Lyude Paul
2020-09-22 17:53 ` [Intel-gfx] " Lyude Paul
2020-09-22 17:53 ` Lyude Paul
2020-09-22 17:53 ` [RESEND PATCH 2/2] drm/dp: fix a kernel-doc issue at drm_edid.c Lyude Paul
2020-09-22 17:53 ` [Intel-gfx] " Lyude Paul
2020-09-22 17:53 ` Lyude Paul
2020-09-22 18:52 ` Patchwork [this message]
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=160080072584.13390.8098876479043768411@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.