From: Jani Nikula <jani.nikula@linux.intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: Introduce struct drm_device based WARN* and use them in i915 (rev4)
Date: Tue, 28 Jan 2020 11:16:31 +0200 [thread overview]
Message-ID: <87o8uo9c0g.fsf@intel.com> (raw)
In-Reply-To: <158015840134.9687.7990172392824281702@emeril.freedesktop.org>
On Mon, 27 Jan 2020, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm: Introduce struct drm_device based WARN* and use them in i915 (rev4)
> URL : https://patchwork.freedesktop.org/series/72035/
> State : failure
I think the repeated attempts with the patches prove that it's really
hard to get patches with such wide impact merged. The driver moves so
fast that things like this probably need to be split up more. For
example per file. It will result in a lot of patches, but at least we
could merge the patches that don't conflict, and keep moving
forward. It's also maybe a bad timing, lots of changes like this going
on atm.
BR,
Jani.
>
> == Summary ==
>
> Applying: drm/i915/display: Make WARN* drm specific where drm_device ptr is available
> Using index info to reconstruct a base tree...
> M drivers/gpu/drm/i915/display/intel_display.c
> M drivers/gpu/drm/i915/display/intel_dp.c
> M drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> M drivers/gpu/drm/i915/display/intel_hdmi.c
> M drivers/gpu/drm/i915/display/intel_hotplug.c
> M drivers/gpu/drm/i915/display/intel_lvds.c
> M drivers/gpu/drm/i915/display/intel_pipe_crc.c
> M drivers/gpu/drm/i915/display/intel_sdvo.c
> Falling back to patching base and 3-way merge...
> Auto-merging drivers/gpu/drm/i915/display/intel_sdvo.c
> Auto-merging drivers/gpu/drm/i915/display/intel_pipe_crc.c
> Auto-merging drivers/gpu/drm/i915/display/intel_lvds.c
> Auto-merging drivers/gpu/drm/i915/display/intel_hotplug.c
> Auto-merging drivers/gpu/drm/i915/display/intel_hdmi.c
> CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/display/intel_hdmi.c
> Auto-merging drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> Auto-merging drivers/gpu/drm/i915/display/intel_dp.c
> Auto-merging drivers/gpu/drm/i915/display/intel_display.c
> CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/display/intel_display.c
> error: Failed to merge in the changes.
> hint: Use 'git am --show-current-patch' to see the failed patch
> Patch failed at 0001 drm/i915/display: Make WARN* drm specific where drm_device ptr is available
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-01-28 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 7:56 [Intel-gfx] [PATCH v4 0/4] drm: Introduce struct drm_device based WARN* and use them in i915 Pankaj Bharadiya
2020-01-27 7:56 ` [Intel-gfx] [PATCH v4 1/4] drm/i915/display: Make WARN* drm specific where drm_device ptr is available Pankaj Bharadiya
2020-01-27 7:56 ` [Intel-gfx] [PATCH v4 2/4] drm/i915/display: Make WARN* drm specific where drm_priv " Pankaj Bharadiya
2020-01-27 7:56 ` [Intel-gfx] [PATCH v4 3/4] drm/i915/gvt: " Pankaj Bharadiya
2020-01-27 7:56 ` [Intel-gfx] [PATCH v4 4/4] drm/i915/gvt: Make WARN* drm specific where vgpu " Pankaj Bharadiya
2020-01-27 20:53 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: Introduce struct drm_device based WARN* and use them in i915 (rev4) Patchwork
2020-01-28 9:16 ` Jani Nikula [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=87o8uo9c0g.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pankaj.laxminarayan.bharadiya@intel.com \
--cc=patchwork@emeril.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