From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: dhowells@redhat.com, keyrings@vger.kernel.org,
herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: asym_tpm: Use common tpm_buf for asymmetric keys
Date: Fri, 13 Sep 2019 13:30:57 +0000 [thread overview]
Message-ID: <20190913133057.GD7412@linux.intel.com> (raw)
In-Reply-To: <1568200910-31368-1-git-send-email-sumit.garg@linaro.org>
On Wed, Sep 11, 2019 at 04:51:50PM +0530, Sumit Garg wrote:
> Switch to utilize common heap based tpm_buf code for TPM based
> asymmetric keys rather than using stack based tpm_buf code.
>
> Reported-by: kbuild test robot <lkp@intel.com>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
Can you roll instead a new version of the whole patch set?
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: dhowells@redhat.com, keyrings@vger.kernel.org,
herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: asym_tpm: Use common tpm_buf for asymmetric keys
Date: Fri, 13 Sep 2019 14:30:57 +0100 [thread overview]
Message-ID: <20190913133057.GD7412@linux.intel.com> (raw)
In-Reply-To: <1568200910-31368-1-git-send-email-sumit.garg@linaro.org>
On Wed, Sep 11, 2019 at 04:51:50PM +0530, Sumit Garg wrote:
> Switch to utilize common heap based tpm_buf code for TPM based
> asymmetric keys rather than using stack based tpm_buf code.
>
> Reported-by: kbuild test robot <lkp@intel.com>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
Can you roll instead a new version of the whole patch set?
/Jarkko
next prev parent reply other threads:[~2019-09-13 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 11:21 [PATCH] KEYS: asym_tpm: Use common tpm_buf for asymmetric keys Sumit Garg
2019-09-11 11:33 ` Sumit Garg
2019-09-13 13:30 ` Jarkko Sakkinen [this message]
2019-09-13 13:30 ` Jarkko Sakkinen
2019-09-16 4:39 ` Sumit Garg
2019-09-16 4:51 ` Sumit Garg
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=20190913133057.GD7412@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.garg@linaro.org \
/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.