stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Computer Enthusiastic <computer.enthusiastic@gmail.com>
To: stable@vger.kernel.org, Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>,
	nouveau@lists.freedesktop.org,
	Salvatore Bonaccorso <carnil@debian.org>,
	Lyude Paul <lyude@redhat.com>
Subject: Re: [Nouveau] [PATCH] nouveau: explicitly wait on the fence in nouveau_bo_move_m2mf
Date: Sat, 28 Jan 2023 15:49:59 +0100	[thread overview]
Message-ID: <cdfc26b5-c045-5f93-b553-942618f0983a@gmail.com> (raw)
In-Reply-To: <CAHSpYy117N0A1QJKVNmFNii3iL9mU71_RusiUo5ZAMcJZciM-g@mail.gmail.com>

Hello,

The patch "[Nouveau] [PATCH] nouveau: explicitly wait on the fence in 
nouveau_bo_move_m2mf" [1] was marked for kernels v5.15+ and it was 
merged upstream.

The same patch [1] works with kernel 5.10.y, but it is not been merged 
upstream so far.

According to Karol Herbst suggestion [2], I'm sending this message to 
ask for merging it into 5.10 kernel.

Thanks in advance.

---
[1] 
https://lore.kernel.org/nouveau/20220819200928.401416-1-kherbst@redhat.com/

[2] 
https://lore.kernel.org/nouveau/CACO55tv0jO2TmuWcwFiAUQB-__DZVwhv7WNN9MfgMXV053gknw@mail.gmail.com/

  parent reply	other threads:[~2023-01-28 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 20:09 [PATCH] nouveau: explicitly wait on the fence in nouveau_bo_move_m2mf Karol Herbst
2022-08-22 21:15 ` Lyude Paul
2022-09-20 10:42 ` Salvatore Bonaccorso
2022-09-20 11:36   ` Karol Herbst
2022-09-20 11:59     ` Salvatore Bonaccorso
2022-09-30 21:09       ` Computer Enthusiastic
2022-11-19  5:20 ` [Nouveau] " Computer Enthusiastic
     [not found] ` <CAHSpYy0HAifr4f+z64h+xFUmMNbB4hCR1r2Z==TsB4WaHatQqg@mail.gmail.com>
     [not found]   ` <CACO55tv0jO2TmuWcwFiAUQB-__DZVwhv7WNN9MfgMXV053gknw@mail.gmail.com>
     [not found]     ` <CAHSpYy117N0A1QJKVNmFNii3iL9mU71_RusiUo5ZAMcJZciM-g@mail.gmail.com>
2023-01-28 14:49       ` Computer Enthusiastic [this message]
2023-01-28 17:51         ` Greg KH
2023-01-28 19:49           ` Salvatore Bonaccorso
2023-01-29 21:36             ` Computer Enthusiastic
2023-01-30 10:05               ` Greg KH
2023-01-30 22:27                 ` Lyude Paul
2023-02-01 19:24                   ` Computer Enthusiastic

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=cdfc26b5-c045-5f93-b553-942618f0983a@gmail.com \
    --to=computer.enthusiastic@gmail.com \
    --cc=bskeggs@redhat.com \
    --cc=carnil@debian.org \
    --cc=kherbst@redhat.com \
    --cc=lyude@redhat.com \
    --cc=nouveau@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).