From: Greg KH <greg@kroah.com>
To: Jocelyn Falempe <jfalempe@redhat.com>
Cc: zack.rusin@broadcom.com, stable@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm/vmwgfx backport two fixes to v6.1.x branch
Date: Mon, 22 Jan 2024 11:01:56 -0800 [thread overview]
Message-ID: <2024012246-affirm-vixen-e598@gregkh> (raw)
In-Reply-To: <20240122172031.243604-1-jfalempe@redhat.com>
On Mon, Jan 22, 2024 at 06:10:11PM +0100, Jocelyn Falempe wrote:
> Hi,
>
> I've backported this two commits:
> f9e96bf19054 drm/vmwgfx: Fix possible invalid drm gem put calls
> 91398b413d03 drm/vmwgfx: Keep a gem reference to user bos in surfaces
>
> They both fixes a950b989ea29 ("drm/vmwgfx: Do not drop the reference
> to the handle too soon")
> which has been backported to v6.1.x branch as 0a127ac97240
>
> There was a lot of conflicts, and as I'm not familiar with the vmwgfx
> driver, it's better to review and test them.
> I've run a short test, and it worked, but that's certainly not enough.
All now queued up, thanks.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Jocelyn Falempe <jfalempe@redhat.com>
Cc: dri-devel@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] drm/vmwgfx backport two fixes to v6.1.x branch
Date: Mon, 22 Jan 2024 11:01:56 -0800 [thread overview]
Message-ID: <2024012246-affirm-vixen-e598@gregkh> (raw)
In-Reply-To: <20240122172031.243604-1-jfalempe@redhat.com>
On Mon, Jan 22, 2024 at 06:10:11PM +0100, Jocelyn Falempe wrote:
> Hi,
>
> I've backported this two commits:
> f9e96bf19054 drm/vmwgfx: Fix possible invalid drm gem put calls
> 91398b413d03 drm/vmwgfx: Keep a gem reference to user bos in surfaces
>
> They both fixes a950b989ea29 ("drm/vmwgfx: Do not drop the reference
> to the handle too soon")
> which has been backported to v6.1.x branch as 0a127ac97240
>
> There was a lot of conflicts, and as I'm not familiar with the vmwgfx
> driver, it's better to review and test them.
> I've run a short test, and it worked, but that's certainly not enough.
All now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2024-01-22 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 17:10 [PATCH 0/2] drm/vmwgfx backport two fixes to v6.1.x branch Jocelyn Falempe
2024-01-22 17:10 ` [PATCH 1/2] drm/vmwgfx: Fix possible invalid drm gem put calls Jocelyn Falempe
2024-01-22 17:10 ` Jocelyn Falempe
2024-01-22 17:10 ` [PATCH 2/2] drm/vmwgfx: Keep a gem reference to user bos in surfaces Jocelyn Falempe
2024-01-22 17:10 ` Jocelyn Falempe
2024-01-22 19:01 ` Greg KH [this message]
2024-01-22 19:01 ` [PATCH 0/2] drm/vmwgfx backport two fixes to v6.1.x branch Greg KH
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=2024012246-affirm-vixen-e598@gregkh \
--to=greg@kroah.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=stable@vger.kernel.org \
--cc=zack.rusin@broadcom.com \
/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.