From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Graf <graf@amazon.de>
Cc: Babis Chalios <bchalios@amazon.es>, Theodore Ts'o <tytso@mit.edu>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
linux-kernel@vger.kernel.org, mzxreary@0pointer.de,
xmarcalx@amazon.co.uk, Amit Shah <amit@kernel.org>
Subject: Re: [PATCH 0/1] User space notifications about VM cloning
Date: Wed, 28 Jun 2023 13:22:11 +0200 [thread overview]
Message-ID: <2023062834-lark-frostbite-9710@gregkh> (raw)
In-Reply-To: <6ccec434-42f0-0ae8-8c7b-bea4646c5e7d@amazon.de>
On Wed, Jun 28, 2023 at 01:13:40PM +0200, Alexander Graf wrote:
> Hi folks,
>
> On 16.06.23 17:07, Babis Chalios wrote:
> > Hello all,
> >
> > Some time has passed since I sent this. Any comments/thoughts?
>
>
> Can we please get this merged somehow? Greg, any advise?
>
> This is purely a device notification event to user space, similar to network
> link change events and the likes and has nothing to do with Jason's
> envisioned random reseed event exposure. We can happily send RFC patches for
> the latter after this is merged too.
Sure, I can take it, but it's the middle of the merge window and it's
too late for anything new right now, sorry.
I'll pick it up after 6.5-rc1 is out.
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-28 11:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:51 [PATCH 0/1] User space notifications about VM cloning Babis Chalios
2023-05-31 9:51 ` [PATCH 1/1] vmgenid: emit uevent when VMGENID updates Babis Chalios
2023-06-19 9:14 ` Alexander Graf
2023-06-19 15:48 ` Lennart Poettering
2023-06-19 20:30 ` Jason A. Donenfeld
2023-06-19 20:37 ` Alexander Graf
2023-06-20 10:27 ` Babis Chalios
2023-06-20 11:28 ` Lennart Poettering
2023-11-14 12:51 ` Alexander Graf
2023-06-16 15:07 ` [PATCH 0/1] User space notifications about VM cloning Babis Chalios
2023-06-28 11:13 ` Alexander Graf
2023-06-28 11:22 ` Greg KH [this message]
2023-06-28 11:36 ` Jason A. Donenfeld
2023-06-28 11:47 ` Greg KH
2023-06-28 16:08 ` Greg KH
2023-06-28 16:27 ` Jason A. Donenfeld
2023-06-28 16:53 ` Amit Shah
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=2023062834-lark-frostbite-9710@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=amit@kernel.org \
--cc=bchalios@amazon.es \
--cc=graf@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mzxreary@0pointer.de \
--cc=tytso@mit.edu \
--cc=xmarcalx@amazon.co.uk \
/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.