From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 1/6] drm/i915: Mark concurrent submissions with a weak-dependency
Date: Wed, 06 May 2020 23:42:15 +0000 [thread overview]
Message-ID: <20200506234216.56CD520746@mail.kernel.org> (raw)
In-Reply-To: <20200504135030.19210-2-chris@chris-wilson.co.uk>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: c81471f5e95c ("drm/i915: Copy across scheduler behaviour flags across submit fences").
The bot has tested the following trees: v5.6.10.
v5.6.10: Failed to apply! Possible dependencies:
8e9f84cf5cac ("drm/i915/gt: Propagate change in error status to children on unhold")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: tvrtko.ursulin@intel.com, lionel.g.landwerlin@intel.com
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/6] drm/i915: Mark concurrent submissions with a weak-dependency
Date: Wed, 06 May 2020 23:42:15 +0000 [thread overview]
Message-ID: <20200506234216.56CD520746@mail.kernel.org> (raw)
In-Reply-To: <20200504135030.19210-2-chris@chris-wilson.co.uk>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: c81471f5e95c ("drm/i915: Copy across scheduler behaviour flags across submit fences").
The bot has tested the following trees: v5.6.10.
v5.6.10: Failed to apply! Possible dependencies:
8e9f84cf5cac ("drm/i915/gt: Propagate change in error status to children on unhold")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-05-06 23:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 13:50 [Intel-gfx] Wait-for-submit on future syncobj Chris Wilson
2020-05-04 13:50 ` [Intel-gfx] [PATCH 1/6] drm/i915: Mark concurrent submissions with a weak-dependency Chris Wilson
2020-05-04 13:50 ` Chris Wilson
2020-05-06 23:42 ` Sasha Levin [this message]
2020-05-06 23:42 ` Sasha Levin
2020-05-04 13:50 ` [Intel-gfx] [PATCH 2/6] dma-buf: Proxy fence, an unsignaled fence placeholder Chris Wilson
2020-05-04 13:50 ` [Intel-gfx] [PATCH 3/6] drm/syncobj: Allow use of dma-fence-proxy Chris Wilson
2020-05-04 13:50 ` [Intel-gfx] [PATCH 4/6] drm/i915/gem: Teach execbuf how to wait on future syncobj Chris Wilson
2020-05-05 13:48 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-05-05 13:53 ` Chris Wilson
2020-05-05 15:02 ` Chris Wilson
2020-05-04 13:50 ` [Intel-gfx] [PATCH 5/6] drm/i915/gem: Allow combining submit-fences with syncobj Chris Wilson
2020-05-04 13:50 ` [Intel-gfx] [PATCH 6/6] drm/i915/gt: Declare when we enabled timeslicing Chris Wilson
2020-05-04 13:54 ` [Intel-gfx] Wait-for-submit on future syncobj Chris Wilson
2020-05-04 14:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Mark concurrent submissions with a weak-dependency Patchwork
2020-05-04 15:08 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-05-05 16:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Mark concurrent submissions with a weak-dependency (rev3) Patchwork
2020-05-05 16:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-05-06 4:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20200506234216.56CD520746@mail.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.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.