From: Petr Vorel <pvorel@suse.cz>
To: linux-crypto@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Nicolai Stange <nstange@suse.de>,
linux-kbuild@vger.kernel.org, Nayna Jain <nayna@linux.ibm.com>,
Paulo Flabiano Smorigo <pfsmorigo@gmail.com>,
leitao@debian.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 1/2] crypto: vmx: Turn CRYPTO_DEV_VMX_ENCRYPT into tristate
Date: Wed, 16 Feb 2022 08:24:10 +0100 [thread overview]
Message-ID: <YgymmnfKZpMzAMro@pevik> (raw)
In-Reply-To: <20220215185936.15576-2-pvorel@suse.cz>
Hi,
I kept CRYPTO_DEV_VMX_ENCRYPT in drivers/crypto/vmx/Kconfig,
but maybe I should have moved it into drivers/crypto/Kconfig.
It's not clear what is preferred.
Kind regards,
Petr
next prev parent reply other threads:[~2022-02-16 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 18:59 [PATCH v2 0/2] vmx-crypto: Add missing dependencies Petr Vorel
2022-02-15 18:59 ` [PATCH v2 1/2] crypto: vmx: Turn CRYPTO_DEV_VMX_ENCRYPT into tristate Petr Vorel
2022-02-16 7:24 ` Petr Vorel [this message]
2022-02-16 9:33 ` Nicolai Stange
2022-02-16 9:57 ` Petr Vorel
2022-02-16 10:01 ` Petr Vorel
2022-02-15 18:59 ` [PATCH v2 2/2] crypto: vmx: Add missing dependencies Petr Vorel
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=YgymmnfKZpMzAMro@pevik \
--to=pvorel@suse.cz \
--cc=herbert@gondor.apana.org.au \
--cc=leitao@debian.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nayna@linux.ibm.com \
--cc=nstange@suse.de \
--cc=pfsmorigo@gmail.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).