From: Vladis Dronov <vdronov@redhat.com>
To: Koba Ko <koba.ko@canonical.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
John Allen <john.allen@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: ccp - Failure on re-initialization due to duplicate sysfs filename
Date: Mon, 9 Jan 2023 12:52:59 +0100 [thread overview]
Message-ID: <CAMusb+SK3SPOijFw2wkivXQbhaJfe1Fhd0XNNv95soZdBP4eRA@mail.gmail.com> (raw)
In-Reply-To: <20230109021502.682474-1-koba.ko@canonical.com>
Hi,
This looks good to me, thanks, Koba:
Reviewed-by: Vladis Dronov <vdronov@redhat.com>
Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
next prev parent reply other threads:[~2023-01-09 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 2:15 [PATCH] crypto: ccp - Failure on re-initialization due to duplicate sysfs filename Koba Ko
2023-01-09 11:52 ` Vladis Dronov [this message]
2023-01-09 14:13 ` Tom Lendacky
2023-01-20 10:32 ` Herbert Xu
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=CAMusb+SK3SPOijFw2wkivXQbhaJfe1Fhd0XNNv95soZdBP4eRA@mail.gmail.com \
--to=vdronov@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=koba.ko@canonical.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.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 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).