From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Babis Chalios <bchalios@amazon.es>
Cc: tytso@mit.edu, robh@kernel.org, krzk@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sudanl@amazon.com, graf@amazon.com,
dwmw@amazon.co.uk, krzysztof.kozlowski@linaro.org
Subject: Re: [PATCH v8 0/3] virt: vmgenid: add devicetree bindings support
Date: Sat, 27 Apr 2024 02:41:25 +0200 [thread overview]
Message-ID: <ZixJta_sWoTsaprk@zx2c4.com> (raw)
In-Reply-To: <ba8e850c-756f-4839-b3d7-db8873f83392@amazon.es>
Hi Babis,
On Mon, Apr 22, 2024 at 03:29:59PM +0200, Babis Chalios wrote:
> I also verified that this still works with ACPI on Firecracker.
> I also verified that the OF part of the patch works with this:
> https://github.com/sudanl0/firecracker/commit/f382e09a9b1e4453d2b231232d89bcb85296ac87
> patch on top of Firecracker.
>
> Tested-by: Babis Chalios <bchalios@amazon.es>
Thanks for testing this. No word from the other folks who were looking
at this patchset before, so I'll move ahead and apply this to
random.git and send it up for 6.10.
- [1/3] https://git.kernel.org/crng/random/c/e07606713
- [2/3] https://git.kernel.org/crng/random/c/a4aded1ff
- [3/3] https://git.kernel.org/crng/random/c/7b1bcd6b5
Jason
prev parent reply other threads:[~2024-04-27 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 22:39 [PATCH v8 0/3] virt: vmgenid: add devicetree bindings support Jason A. Donenfeld
2024-04-19 22:39 ` [PATCH v8 1/3] virt: vmgenid: change implementation to use a platform driver Jason A. Donenfeld
2024-04-19 22:39 ` [PATCH v8 2/3] dt-bindings: rng: Add vmgenid support Jason A. Donenfeld
2024-04-19 22:40 ` [PATCH v8 3/3] virt: vmgenid: add support for devicetree bindings Jason A. Donenfeld
2024-04-22 13:29 ` [PATCH v8 0/3] virt: vmgenid: add devicetree bindings support Babis Chalios
2024-04-27 0:41 ` Jason A. Donenfeld [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=ZixJta_sWoTsaprk@zx2c4.com \
--to=jason@zx2c4.com \
--cc=bchalios@amazon.es \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=graf@amazon.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sudanl@amazon.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).