devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Babis Chalios <bchalios@amazon.es>,
	tytso@mit.edu, Jason@zx2c4.com, olivia@selenic.com,
	herbert@gondor.apana.org.au, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-crypto@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: sudanl@amazon.com, graf@amazon.de, xmarcalx@amazon.co.uk,
	dwmw@amazon.co.uk
Subject: Re: [PATCH v5 4/5] dt-bindings: rng: Add vmgenid support
Date: Wed, 17 Apr 2024 15:16:08 +0200	[thread overview]
Message-ID: <71006589-c725-481d-be99-7ca1857d1e33@kernel.org> (raw)
In-Reply-To: <20240417081212.99657-5-bchalios@amazon.es>

On 17/04/2024 10:12, Babis Chalios wrote:
> From: Sudan Landge <sudanl@amazon.com>
> 
> Virtual Machine Generation ID driver was introduced in commit af6b54e2b5ba
> ("virt: vmgenid: notify RNG of VM fork and supply generation ID"), as an
> ACPI only device.
> 

This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions, under or above your Signed-off-by tag. Tag is "received", when
provided in a message replied to you on the mailing list. Tools like b4
can help here. However, there's no need to repost patches *only* to add
the tags. The upstream maintainer will do that for tags received on the
version they apply.

https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.

Best regards,
Krzysztof


  parent reply	other threads:[~2024-04-17 13:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17  8:12 [PATCH v5 0/5] virt: vmgenid: Add devicetree bindings support Babis Chalios
2024-04-17  8:12 ` [PATCH v5 1/5] virt: vmgenid: rearrange code to make review easier Babis Chalios
2024-04-17  8:35   ` Alexander Graf
2024-04-17  9:05     ` Babis Chalios
2024-04-17  9:12       ` Alexander Graf
2024-04-17 12:42       ` Jason A. Donenfeld
2024-04-17 13:19         ` Krzysztof Kozlowski
2024-04-17  8:12 ` [PATCH v5 2/5] virt: vmgenid: change implementation to use a platform driver Babis Chalios
2024-04-17  8:12 ` [PATCH v5 3/5] virt: vmgenid: enable driver regardless of ACPI config Babis Chalios
2024-04-17  8:12 ` [PATCH v5 4/5] dt-bindings: rng: Add vmgenid support Babis Chalios
2024-04-17  8:41   ` Alexander Graf
2024-04-17 13:16   ` Krzysztof Kozlowski [this message]
2024-04-17 13:16   ` Krzysztof Kozlowski
2024-04-17  8:12 ` [PATCH v5 5/5] virt: vmgenid: add support for devicetree bindings Babis Chalios
2024-04-17 13:17   ` Krzysztof Kozlowski
2024-04-17  8:44 ` [PATCH v5 0/5] virt: vmgenid: Add devicetree bindings support Alexander Graf

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=71006589-c725-481d-be99-7ca1857d1e33@kernel.org \
    --to=krzk@kernel.org \
    --cc=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.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olivia@selenic.com \
    --cc=robh@kernel.org \
    --cc=sudanl@amazon.com \
    --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 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 NNTP newsgroup(s).