From: Patchwork <patchwork@annarchy.freedesktop.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915/dsi: i2c/gpio (rev3)
Date: Fri, 05 Feb 2016 07:31:32 -0000 [thread overview]
Message-ID: <20160205073132.29975.1057@annarchy.freedesktop.org> (raw)
In-Reply-To: <cover.1454582914.git.jani.nikula@intel.com>
== Summary ==
Series 3075v3 drm/i915/dsi: i2c/gpio
2016-02-04T16:55:25.384210 http://patchwork.freedesktop.org/api/1.0/series/3075/revisions/3/mbox/
Applying: drm/i915/dsi: defend gpio table against out of bounds access
Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
Applying: drm/i915/dsi: don't pass arbitrary data to sideband
Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
Patch failed at 0002 drm/i915/dsi: don't pass arbitrary data to sideband
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-05 7:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 10:50 [PATCH 0/8] drm/i915/dsi: i2c/gpio Jani Nikula
2016-02-04 10:50 ` [PATCH 1/8] drm/i915/dsi: defend gpio table against out of bounds access Jani Nikula
2016-02-04 15:40 ` Ville Syrjälä
2016-02-04 10:50 ` [PATCH 2/8] drm/i915/dsi: don't pass arbitrary data to sideband Jani Nikula
2016-02-04 15:41 ` Ville Syrjälä
2016-02-04 16:56 ` Jani Nikula
2016-02-04 10:50 ` [PATCH 3/8] drm/i915: Adding the parsing logic for the i2c element Jani Nikula
2016-02-04 15:28 ` Ville Syrjälä
2016-02-04 16:21 ` Jani Nikula
2016-02-04 16:36 ` Ville Syrjälä
2016-02-15 16:48 ` Daniel Vetter
2016-02-04 10:50 ` [PATCH 4/8] drm/i915/dsi: skip gpio element execution when not supported Jani Nikula
2016-02-04 15:36 ` Ville Syrjälä
2016-02-04 16:52 ` [PATCH v2] " Jani Nikula
2016-02-04 17:05 ` Ville Syrjälä
2016-02-04 17:10 ` Jani Nikula
2016-02-04 17:12 ` Jani Nikula
2016-02-04 17:18 ` Ville Syrjälä
2016-02-04 17:22 ` Jani Nikula
2016-02-04 17:48 ` Ville Syrjälä
2016-02-04 17:49 ` Ville Syrjälä
2016-02-04 18:39 ` Jani Nikula
2016-02-04 10:50 ` [PATCH 5/8] drm/i915: put the IOSF port defines in numerical order Jani Nikula
2016-02-04 16:05 ` Ville Syrjälä
2016-02-04 10:50 ` [PATCH 6/8] drm/i915/vlv: drop unused vlv_gps_core_read/write functions Jani Nikula
2016-02-04 16:12 ` Ville Syrjälä
2016-02-04 16:57 ` Jani Nikula
2016-02-04 10:50 ` [PATCH 7/8] drm/i915: Extend gpio read/write to other cores Jani Nikula
2016-02-04 15:39 ` Ville Syrjälä
2016-02-04 16:55 ` [PATCH v5] " Jani Nikula
2016-02-04 17:03 ` Ville Syrjälä
2016-02-04 17:14 ` Jani Nikula
2016-02-04 10:50 ` [PATCH 8/8] drm/i915/dsi: Added the generic gpio sequence support and gpio table Jani Nikula
2016-02-04 17:51 ` Ville Syrjälä
2016-02-04 12:46 ` ✓ Fi.CI.BAT: success for drm/i915/dsi: i2c/gpio Patchwork
2016-02-05 7:31 ` 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=20160205073132.29975.1057@annarchy.freedesktop.org \
--to=patchwork@annarchy.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).