From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: Re: ✓ Fi.CI.IGT: success for drm/i915: Guc code reorg
Date: Wed, 04 Oct 2017 19:50:26 +0300 [thread overview]
Message-ID: <1507135826.5856.19.camel@linux.intel.com> (raw)
In-Reply-To: <20171003183303.18565.22088@emeril.freedesktop.org>
On Tue, 2017-10-03 at 18:33 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Guc code reorg
> URL : https://patchwork.freedesktop.org/series/31340/
> State : success
I've merged the series, thanks for the patches and review.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-10-04 16:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 16:35 [PATCH v3 0/9] drm/i915: Guc code reorg Michal Wajdeczko
2017-10-03 16:35 ` [PATCH v3 1/9] drm/i915: Make intel_uncore.h header self-contained Michal Wajdeczko
2017-10-03 17:02 ` Chris Wilson
2017-10-03 18:16 ` Michal Wajdeczko
2017-10-03 16:36 ` [PATCH v3 2/9] drm/i915/uc: Drop unnecessary forward declaration Michal Wajdeczko
2017-10-03 16:36 ` [PATCH v3 3/9] drm/i915/uc: Create intel_uc_init_mmio Michal Wajdeczko
2017-10-03 16:36 ` [PATCH v3 4/9] drm/i915/uc: Move uC fw helper code into dedicated files Michal Wajdeczko
2017-10-04 14:23 ` Joonas Lahtinen
2017-10-04 14:54 ` Michal Wajdeczko
2017-10-03 16:36 ` [PATCH v3 5/9] drm/i915/huc: Move HuC declarations into dedicated header Michal Wajdeczko
2017-10-03 16:36 ` [PATCH v3 6/9] drm/i915/guc: Move Guc early init into own function Michal Wajdeczko
2017-10-04 14:26 ` Joonas Lahtinen
2017-10-03 16:36 ` [PATCH v3 7/9] drm/i915/guc: Move GuC log declarations into dedicated header Michal Wajdeczko
2017-10-03 17:03 ` Chris Wilson
2017-10-03 18:28 ` Michal Wajdeczko
2017-10-03 19:48 ` Chris Wilson
2017-10-04 17:09 ` Chris Wilson
2017-10-03 16:36 ` [PATCH v3 8/9] drm/i915/guc: Move GuC submission " Michal Wajdeczko
2017-10-04 17:11 ` Chris Wilson
2017-10-03 16:36 ` [PATCH v3 9/9] drm/i915/guc: Move GuC core definitions into dedicated files Michal Wajdeczko
2017-10-04 17:17 ` Chris Wilson
2017-10-05 15:40 ` Michal Wajdeczko
2017-10-03 17:16 ` ✓ Fi.CI.BAT: success for drm/i915: Guc code reorg Patchwork
2017-10-03 18:33 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-04 16:50 ` Joonas Lahtinen [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=1507135826.5856.19.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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