From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
"Sasha Levin" <sashal@kernel.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 0/3] Stable backports of gntdev fixes
Date: Mon, 31 Oct 2022 16:22:54 -0400 [thread overview]
Message-ID: <Y2Aun1V6TMRwtx15@itl-email> (raw)
In-Reply-To: <Y194Q9lH3ye4jJOU@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On Mon, Oct 31, 2022 at 08:24:51AM +0100, Greg Kroah-Hartman wrote:
> On Sun, Oct 30, 2022 at 03:12:40AM -0400, Demi Marie Obenour wrote:
> > I backported the recent gntdev patches to stable branches before 5.15.
> > The first patch is a prerequisite for the other backports. The second
> > patch should apply cleanly to all stable branches, but the third only
> > applies to 5.10 as it requires mmu_interval_notifier_insert_locked().
>
> Patches 1 and 2 now queued up, see my comments on 3.
Thanks!
--
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-10-31 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 7:12 [PATCH 0/3] Stable backports of gntdev fixes Demi Marie Obenour
2022-10-30 7:12 ` [PATCH 1/3] Xen/gntdev: don't ignore kernel unmapping error Demi Marie Obenour
2022-10-30 7:12 ` [PATCH 2/3] xen/gntdev: Prevent leaking grants Demi Marie Obenour
2022-10-30 7:12 ` [PATCH 3/3] xen/gntdev: Accommodate VMA splitting Demi Marie Obenour
2022-10-31 7:24 ` Greg Kroah-Hartman
2022-10-31 20:27 ` Demi Marie Obenour
2022-10-31 7:24 ` [PATCH 0/3] Stable backports of gntdev fixes Greg Kroah-Hartman
2022-10-31 20:22 ` Demi Marie Obenour [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=Y2Aun1V6TMRwtx15@itl-email \
--to=demi@invisiblethingslab.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sashal@kernel.org \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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 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.