From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 1/4] drm-tip: 2019y-04m-18d-17h-03m-51s UTC integration manifest
Date: Fri, 19 Apr 2019 12:15:58 +0100 [thread overview]
Message-ID: <20190419111601.18656-1-chris@chris-wilson.co.uk> (raw)
From: Eric Anholt <eric@anholt.net>
---
integration-manifest | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
create mode 100644 integration-manifest
diff --git a/integration-manifest b/integration-manifest
new file mode 100644
index 000000000000..09ab7d222dde
--- /dev/null
+++ b/integration-manifest
@@ -0,0 +1,30 @@
+drm drm-fixes 00fd14ff3017f64a9a03a08291e4be0d87bedc17
+ Merge branch 'drm-fixes-5.1' of git://people.freedesktop.org/~agd5f/linux into drm-fixes
+drm-misc drm-misc-fixes f5a9ed867c83875546c9aadd4ed8e785e9adcc3c
+ drm/sun4i: Fix component unbinding and component master deletion
+drm-intel drm-intel-fixes f5c58ba18ab8ea2169670ed880e4d31ed772ad10
+ drm/i915: Restore correct bxt_ddi_phy_calc_lane_lat_optim_mask() calculation
+drm-amd drm-amd-fixes 2b702e72e33bbdec0764cfb6e1dd00fe1142ae55
+ Merge tag 'drm-misc-fixes-2017-09-28-1' of git://anongit.freedesktop.org/git/drm-misc into drm-fixes
+drm drm-next dbb92471674a48892f5e50779425e03388073ab9
+ Revert "drm: allow render capable master with DRM_AUTH ioctls"
+drm-misc drm-misc-next-fixes c34674a23d1e8674ac532bf3397333f24a41e7b2
+ drm/qxl: remove conflicting framebuffers earlier
+drm-intel drm-intel-next-fixes ca22f32a6296cbfa29de56328c8505560a18cfa8
+ drm/i915: Relax mmap VMA check
+drm-amd drm-amd-next-fixes 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e
+ Linux 4.14-rc1
+drm-misc drm-misc-next dffa9b7a78c4361e55e21b3acb54e0d34ad15ea0
+ drm/v3d: Add missing implicit synchronization.
+drm-intel drm-intel-next-queued 26ddc068de47e2a7cbbd06c915dca7a0dc22c499
+ drm/i915: Setup the RCS ring prior to execution
+drm-intel drm-intel-next ad2c467aa92e283e9e8009bb9eb29a5c6a2d1217
+ drm/i915: Update DRIVER_DATE to 20190417
+drm-amd drm-amd-next 754270c7c56292e97d0eff924a5d5d83f92add07
+ Merge branch 'drm-next-4.15' of git://people.freedesktop.org/~agd5f/linux into drm-next
+sound-upstream for-linus b26e36b7ef36a8a3a147b1609b2505f8a4ecf511
+ ALSA: hda/realtek - add two more pin configuration sets to quirk table
+sound-upstream for-next 442e321ed223d9c01a444c6f874e32fb283c17d2
+ ALSA: ps3: Remove set but not used variables 'start_vaddr' and 'pcm_index'
+drm-intel topic/core-for-CI b573fba52f339dc4fadef7282af4a9413fd6173d
+ ICL HACK: Disable ACPI idle driver
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-04-19 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 11:15 Chris Wilson [this message]
2019-04-19 11:15 ` [PATCH 2/4] drm/i915/ringbuffer: EMIT_INVALIDATE *before* switch context Chris Wilson
2019-04-19 11:16 ` [PATCH 3/4] drm/i915: Enable render context support for Ironlake (gen5) Chris Wilson
2019-04-19 11:16 ` [PATCH 4/4] drm/i915: Enable render context support for gen4 (Broadwater to Cantiga) Chris Wilson
2019-04-19 16:54 ` Kenneth Graunke
2019-04-19 11:17 ` [PATCH 1/4] drm-tip: 2019y-04m-18d-17h-03m-51s UTC integration manifest Chris Wilson
2019-04-19 11:25 ` ✗ Fi.CI.BAT: failure for series starting with [1/4] " Patchwork
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=20190419111601.18656-1-chris@chris-wilson.co.uk \
--to=chris@chris-wilson.co.uk \
--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 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.