Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BUILD: failure for drm: Add privacy-screen class and connector properties
Date: Wed, 8 Jul 2020 21:33:20 +0200	[thread overview]
Message-ID: <1d1cfdd5-c374-e9a7-0933-7fdaf52cf306@redhat.com> (raw)
In-Reply-To: <159422753061.3840.8177250694982350295@emeril.freedesktop.org>

Hi,

On 7/8/20 6:58 PM, Patchwork wrote:
> == Series Details ==
> 
> Series: drm: Add privacy-screen class and connector properties
> URL   : https://patchwork.freedesktop.org/series/79259/
> State : failure
> 
> == Summary ==
> 
> Applying: drm/connector: Fix kerneldoc warning
> Using index info to reconstruct a base tree...
> M	drivers/gpu/drm/drm_connector.c
> Falling back to patching base and 3-way merge...
> Auto-merging drivers/gpu/drm/drm_connector.c
> CONFLICT (content): Merge conflict in drivers/gpu/drm/drm_connector.c

So I was testing on top of 5.8-rc4, I guess I need to rebase this
on dinq. But I'm sure that there will be review comments and my
main reason for posting this v1 was to get feedback, not to get
this CI-ed. So please do review this despite it not cleanly
applying on current dinq. If it not applying somehow impends
reviewing this, please let me know.

Regards,

Hans

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-07-08 19:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 16:43 [Intel-gfx] [PATCH 0/9] drm: Add privacy-screen class and connector properties Hans de Goede
2020-07-08 16:43 ` [Intel-gfx] [PATCH 1/9] drm/connector: Fix kerneldoc warning Hans de Goede
2020-07-08 21:26   ` Alex Deucher
2020-07-08 16:43 ` [Intel-gfx] [PATCH 2/9] drm/connector: Add support for privacy-screen properties (v4) Hans de Goede
2020-07-08 16:43 ` [Intel-gfx] [PATCH 3/9] drm: Add privacy-screen class Hans de Goede
2020-07-08 16:43 ` [Intel-gfx] [PATCH 4/9] drm/privacy-screen: Add X86 specific arch init code Hans de Goede
2020-07-08 16:43 ` [Intel-gfx] [PATCH 5/9] drm/privacy-screen: Add notifier support Hans de Goede
2020-07-08 16:43 ` [Intel-gfx] [PATCH 6/9] drm/connector: Add a drm_connector privacy-screen helper functions Hans de Goede
2020-07-08 20:15   ` kernel test robot
2020-07-08 20:57   ` kernel test robot
2020-07-08 16:43 ` [Intel-gfx] [PATCH 7/9] platform/x86: thinkpad_acpi: Get privacy-screen / lcdshadow ACPI handles only once Hans de Goede
2020-07-08 16:43 ` [Intel-gfx] [PATCH 8/9] platform/x86: thinkpad_acpi: Register a privacy-screen device Hans de Goede
2020-07-08 21:45   ` kernel test robot
2020-07-08 16:43 ` [Intel-gfx] [PATCH 9/9] drm/i915: Add privacy-screen support Hans de Goede
2020-07-08 16:58 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: Add privacy-screen class and connector properties Patchwork
2020-07-08 19:33   ` Hans de Goede [this message]
2020-07-08 21:25 ` [Intel-gfx] [PATCH 0/9] " Alex Deucher
2020-07-09 12:48   ` Hans de Goede
2020-07-14 15:00     ` Alex Deucher

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=1d1cfdd5-c374-e9a7-0933-7fdaf52cf306@redhat.com \
    --to=hdegoede@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox