public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	stable <stable@vger.kernel.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Jon Bloomfield <jon.bloomfield@intel.com>
Subject: Re: [PATCH] Revert "drm/i915/gem: Asynchronous cmdparser"
Date: Tue, 27 Jul 2021 17:44:53 +0200	[thread overview]
Message-ID: <YQAp9f1ly39Cbc13@kroah.com> (raw)
In-Reply-To: <CAOFGe97sM_GgZV=BCx8HnrJ2q4UD8eGcsZky2RzhALd9W7gw=A@mail.gmail.com>

On Tue, Jul 27, 2021 at 10:22:01AM -0500, Jason Ekstrand wrote:
> On Tue, Jul 27, 2021 at 5:41 AM Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> >
> > On Tue, Jul 27, 2021 at 7:15 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Mon, Jul 26, 2021 at 06:15:48PM -0500, Jason Ekstrand wrote:
> > > > commit 93b713304188844b8514074dc13ffd56d12235d3 upstream.  This version
> > > > applies to the 5.10 tree.
> > >
> > > I do not see that commit id in Linus's tree, are you sure it is correct?
> >
> > 3761baae908a ("Revert "drm/i915: Propagate errors on awaiting already
> > signaled fences"")
> >
> > Jason, you need to pick the sha1 from drm-intel-fixes, which
> > cherry-picks. Confuses -stable otherwise.
> 
> Sorry.  Do you want me to re-send with correct reference SHAs?

Please do so, I can not take the existing patches for obvious reasons.

thanks,

greg k-h

      reply	other threads:[~2021-07-27 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 23:15 [PATCH] Revert "drm/i915/gem: Asynchronous cmdparser" Jason Ekstrand
2021-07-27  5:14 ` Greg KH
2021-07-27 10:41   ` Daniel Vetter
2021-07-27 15:22     ` Jason Ekstrand
2021-07-27 15:44       ` Greg KH [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=YQAp9f1ly39Cbc13@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=jason@jlekstrand.net \
    --cc=jon.bloomfield@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --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