From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "Conselvan De Oliveira,
Ander" <ander.conselvan.de.oliveira@intel.com>,
Kenneth Graunke <kenneth@whitecape.org>,
intel-gfx@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: Fixes that failed to backport to v4.11-rc1
Date: Tue, 14 Mar 2017 12:56:03 +0200 [thread overview]
Message-ID: <87d1dkdt4s.fsf@intel.com> (raw)
In-Reply-To: <87pohktidd.fsf@intel.com>
On Tue, 14 Mar 2017, Jani Nikula <jani.nikula@intel.com> wrote:
> Thank you for the backports. I'll likely send a pull request of the
> stuff I have in -fixes now, apply these, and let them simmer until next
> week's pull.
I sent the fixes pull request for -rc3, and pushed Chris' backports
after that, thanks again.
I changed the "Cherry-pick: $sha" style annotations to "(cherry picked
from commit $sha)" style, because that's what my current scripts use and
expect. Better to avoid confusion, regardless of which style would
objectively make more sense. I just picked the style because it comes
out of the box with git cherry-pick -x.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-14 10:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 16:14 Fixes that failed to backport to v4.11-rc1 Jani Nikula
2017-03-13 16:59 ` [PATCH 1/2] drm/i915: Split GEM resetting into 3 phases Chris Wilson
2017-03-13 16:59 ` [PATCH 2/2] drm/i915: Disable engine->irq_tasklet around resets Chris Wilson
2017-03-13 17:02 ` [PATCH] drm/i915: Only enable hotplug interrupts if the display interrupts are enabled Chris Wilson
2017-03-15 20:39 ` Lyude Paul
2017-03-13 17:04 ` [PATCH] drm/i915: Drop support for I915_EXEC_CONSTANTS_* execbuf parameters Chris Wilson
2017-03-13 17:06 ` [PATCH] drm/i915: Stop using RP_DOWN_EI on Baytrail Chris Wilson
2017-03-13 21:23 ` Fixes that failed to backport to v4.11-rc1 Chris Wilson
2017-03-14 7:41 ` Jani Nikula
2017-03-14 10:56 ` Jani Nikula [this message]
2017-03-15 9:24 ` Jani Nikula
2017-03-15 9:57 ` [PATCH] drm/i915/glk: Remove MODULE_FIRMWARE() tag from Geminilake's DMC Ander Conselvan de Oliveira
2017-03-15 10:44 ` Jani Nikula
2017-03-15 11:04 ` Fixes that failed to backport to v4.11-rc1 Ville Syrjälä
2017-03-15 14:31 ` [PATCH 4.11] drm/i915: Do .init_clock_gating() earlier to avoid it clobbering watermarks ville.syrjala
2017-03-16 8:06 ` Jani Nikula
2017-03-21 14:23 ` Fixes that failed to backport to v4.11-rc1 Jani Nikula
2017-03-21 14:45 ` [PATCH] drm/i915: Avoid rcu_barrier() from reclaim paths (shrinker) Chris Wilson
2017-03-21 14:47 ` [PATCH] drm/i915: make context status notifier head be per engine Chris Wilson
2017-03-21 14:48 ` Fixes that failed to backport to v4.11-rc1 Chris Wilson
2017-03-21 15:02 ` Jani Nikula
2017-03-29 10:45 ` Jani Nikula
2017-03-29 12:13 ` [PATCH] drm/i915/execlists: Wrap tail pointer after reset tweaking Chris Wilson
2017-03-29 12:13 ` Fixes that failed to backport to v4.11-rc1 Chris Wilson
2017-03-29 12:49 ` Jani Nikula
2017-04-11 12:21 ` Jani Nikula
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=87d1dkdt4s.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kenneth@whitecape.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