public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Computer Enthusiastic <computer.enthusiastic@gmail.com>
Cc: stable@vger.kernel.org, Karol Herbst <kherbst@redhat.com>,
	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 18:51:08 +0100	[thread overview]
Message-ID: <Y9VgjLneuqkl+Y87@kroah.com> (raw)
In-Reply-To: <cdfc26b5-c045-5f93-b553-942618f0983a@gmail.com>

On Sat, Jan 28, 2023 at 03:49:59PM +0100, Computer Enthusiastic wrote:
> 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.

We need to know the git commit id.  And have you tested it on 5.10.y?
And why are you stuck on 5.10.y for this type of hardware?  Why not move
to 5.15.y or 6.1.y?

And as my bot says:

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

thanks,

greg k-h

  reply	other threads:[~2023-01-28 17:51 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
2023-01-28 17:51         ` Greg KH [this message]
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=Y9VgjLneuqkl+Y87@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bskeggs@redhat.com \
    --cc=carnil@debian.org \
    --cc=computer.enthusiastic@gmail.com \
    --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