From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo.com>
Cc: stable@vger.kernel.org, manfred@colorfullife.com,
"Eric W. Biederman" <ebiederm@xmission.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Andrei Vagin <avagin@gmail.com>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Vasily Averin <vvs@virtuozzo.com>
Subject: Re: [PATCH] shm: extend forced shm destroy to support objects from several IPC nses
Date: Tue, 30 Nov 2021 11:33:24 +0100 [thread overview]
Message-ID: <YaX99Dc28F8t6Noo@kroah.com> (raw)
In-Reply-To: <20211129194914.827672-1-alexander.mikhalitsyn@virtuozzo.com>
On Mon, Nov 29, 2021 at 10:49:14PM +0300, Alexander Mikhalitsyn wrote:
> For 4.9.y:
>
> Upstream commit 85b6d24646e4 ("shm: extend forced shm destroy to support objects from several IPC nses")
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2021-11-30 10:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 12:21 FAILED: patch "[PATCH] shm: extend forced shm destroy to support objects from" failed to apply to 4.9-stable tree gregkh
2021-11-29 19:49 ` [PATCH] shm: extend forced shm destroy to support objects from several IPC nses Alexander Mikhalitsyn
2021-11-30 10:33 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-22 12:24 FAILED: patch "[PATCH] shm: extend forced shm destroy to support objects from" failed to apply to 5.10-stable tree gregkh
2021-11-28 13:05 ` [PATCH] shm: extend forced shm destroy to support objects from several IPC nses Manfred Spraul
2021-11-22 12:23 FAILED: patch "[PATCH] shm: extend forced shm destroy to support objects from" failed to apply to 5.4-stable tree gregkh
2021-11-28 15:50 ` [PATCH] shm: extend forced shm destroy to support objects from several IPC nses Manfred Spraul
2021-11-29 12:44 ` Greg KH
2021-11-22 12:22 FAILED: patch "[PATCH] shm: extend forced shm destroy to support objects from" failed to apply to 4.19-stable tree gregkh
2021-11-29 18:44 ` [PATCH] shm: extend forced shm destroy to support objects from several IPC nses Manfred Spraul
2021-12-01 9:09 ` Greg KH
2021-11-22 12:21 FAILED: patch "[PATCH] shm: extend forced shm destroy to support objects from" failed to apply to 4.14-stable tree gregkh
2021-11-29 19:47 ` [PATCH] shm: extend forced shm destroy to support objects from several IPC nses Alexander Mikhalitsyn
2021-11-30 9:56 ` Manfred Spraul
2021-11-30 10:32 ` Greg KH
2021-11-22 12:21 FAILED: patch "[PATCH] shm: extend forced shm destroy to support objects from" failed to apply to 4.4-stable tree gregkh
2021-11-29 16:43 ` [PATCH] shm: extend forced shm destroy to support objects from several IPC nses Alexander Mikhalitsyn
2021-11-29 17:27 ` Greg KH
2021-11-29 20:12 ` Manfred Spraul
2021-11-29 20:22 ` Alexander Mikhalitsyn
2021-11-30 10:34 ` Greg KH
2021-11-08 19:04 [to-be-updated] shm-extend-forced-shm-destroy-to-support-objects-from-several-ipc-nses.patch removed from -mm tree akpm
2021-11-09 15:15 ` [PATCH] shm: extend forced shm destroy to support objects from several IPC nses Manfred Spraul
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=YaX99Dc28F8t6Noo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.mikhalitsyn@virtuozzo.com \
--cc=avagin@gmail.com \
--cc=dave@stgolabs.net \
--cc=ebiederm@xmission.com \
--cc=manfred@colorfullife.com \
--cc=ptikhomirov@virtuozzo.com \
--cc=stable@vger.kernel.org \
--cc=vvs@virtuozzo.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.