Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 0/2] BACKPORT: drm/i915: Get rid of fence error propagation
Date: Mon, 2 Aug 2021 15:21:48 -0400	[thread overview]
Message-ID: <YQhFzBTglOJMSC1k@sashalap> (raw)
In-Reply-To: <20210802184802.414849-1-jason@jlekstrand.net>

On Mon, Aug 02, 2021 at 01:48:00PM -0500, Jason Ekstrand wrote:
>This is a back-port of the following patches from torvalds/master to 5.10:
>
> - 686c7c35abc2 ("drm/i915/gem: Asynchronous cmdparser")
> - 9e31c1fe45d5 ("drm/i915: Propagate errors on awaiting already signaled fences")
>
>Jason Ekstrand (2):
>  drm/i915: Revert "drm/i915/gem: Asynchronous cmdparser"
>  Revert "drm/i915: Propagate errors on awaiting already signaled
>    fences"
>
> .../gpu/drm/i915/gem/i915_gem_execbuffer.c    | 164 +-----------------
> drivers/gpu/drm/i915/i915_cmd_parser.c        |  28 +--
> drivers/gpu/drm/i915/i915_request.c           |   8 +-
> 3 files changed, 27 insertions(+), 173 deletions(-)

Queued up, thanks!

-- 
Thanks,
Sasha

  parent reply	other threads:[~2021-08-02 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 18:48 [PATCH 0/2] BACKPORT: drm/i915: Get rid of fence error propagation Jason Ekstrand
2021-08-02 18:48 ` [PATCH 1/2] drm/i915: Revert "drm/i915/gem: Asynchronous cmdparser" Jason Ekstrand
2021-08-02 18:48 ` [PATCH 2/2] Revert "drm/i915: Propagate errors on awaiting already signaled fences" Jason Ekstrand
2021-08-02 19:21 ` Sasha Levin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-02 18:48 [PATCH 0/2] BACKPORT: drm/i915: Get rid of fence error propagation Jason Ekstrand
2021-08-02 19:21 ` Sasha Levin

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=YQhFzBTglOJMSC1k@sashalap \
    --to=sashal@kernel.org \
    --cc=jason@jlekstrand.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox