From: "Thomas, Rijo-john" <Rijo-john.Thomas@amd.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Hook, Gary" <Gary.Hook@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"Singh, Brijesh" <brijesh.singh@amd.com>,
"Easow, Nimesh" <Nimesh.Easow@amd.com>,
"Rangasamy, Devaraj" <Devaraj.Rangasamy@amd.com>
Subject: Re: [RFC PATCH 1/5] crypto: ccp - rename psp-dev files to sev-dev
Date: Thu, 24 Oct 2019 11:19:37 +0000 [thread overview]
Message-ID: <e474bce6-8189-2c47-f61c-3c57532a43fd@amd.com> (raw)
In-Reply-To: <CAKv+Gu8Dtqr-=71e_P-h=+yBLxzyTcnp4EKsh8q_nGsXYvLL4A@mail.gmail.com>
Hello Ard,
On 23/10/19 5:18 PM, Ard Biesheuvel wrote:
> Hello Thomas,
>
> On Wed, 23 Oct 2019 at 13:27, Thomas, Rijo-john
> <Rijo-john.Thomas@amd.com> wrote:
>>
>> This is a preliminary patch for creating a generic PSP device driver
>> file, which will have support for both SEV and TEE (Trusted Execution
>> Environment) interface.
>>
>> This patch does not introduce any new functionality, but simply renames
>> psp-dev.c and psp-dev.h files to sev-dev.c and sev-dev.h files
>> respectively.
>>
>> Signed-off-by: Rijo Thomas <Rijo-john.Thomas@amd.com>
>> Signed-off-by: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>
>
> This is not the correct way to credit a co-author.
>
> You are sending the patch, so your signoff should come last.
>
> If Devaraj is a co-author of this work, you should add the following
> lines *before* your signoff
>
> Co-authored-by: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>
> Signed-off-by: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>
>
> If Devaraj is the sole author of this work, and you are just sending
> it out, you should set the authorship on the patch to Devaraj (so it
> will be From: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>)
>
Okay, in my next patch revision I shall correct this.
Devaraj is the co-author.
So, the lines would like like:
Co-authored-by: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>
Signed-off-by: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>
Signed-off-by: Rijo Thomas <Rijo-john.Thomas@amd.com>
>> ---
>> drivers/crypto/ccp/Makefile | 2 +-
>> drivers/crypto/ccp/psp-dev.c | 1087 ------------------------------------------
>> drivers/crypto/ccp/psp-dev.h | 66 ---
>> drivers/crypto/ccp/sev-dev.c | 1087 ++++++++++++++++++++++++++++++++++++++++++
>> drivers/crypto/ccp/sev-dev.h | 66 +++
>> drivers/crypto/ccp/sp-pci.c | 2 +-
>> 6 files changed, 1155 insertions(+), 1155 deletions(-)
>> delete mode 100644 drivers/crypto/ccp/psp-dev.c
>> delete mode 100644 drivers/crypto/ccp/psp-dev.h
>> create mode 100644 drivers/crypto/ccp/sev-dev.c
>> create mode 100644 drivers/crypto/ccp/sev-dev.h
>>
>
> Please regenerate the patch so that the rename is reflected in the diffstat.
>
Okay, I will regenerate the patch with proper diffstat.
Thanks,
Rijo
next prev parent reply other threads:[~2019-10-24 11:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 11:27 [RFC PATCH 0/5] Add TEE interface support to AMD Secure Processor driver Thomas, Rijo-john
2019-10-23 11:27 ` [RFC PATCH 1/5] crypto: ccp - rename psp-dev files to sev-dev Thomas, Rijo-john
2019-10-23 11:48 ` Ard Biesheuvel
2019-10-24 11:19 ` Thomas, Rijo-john [this message]
2019-10-23 11:27 ` [RFC PATCH 2/5] crypto: ccp - create a generic psp-dev file Thomas, Rijo-john
2019-10-23 11:27 ` [RFC PATCH 3/5] crypto: ccp - move SEV vdata to a dedicated data structure Thomas, Rijo-john
2019-10-23 11:27 ` [RFC PATCH 4/5] crypto: ccp - add TEE support for Raven Ridge Thomas, Rijo-john
2019-10-23 11:49 ` Ard Biesheuvel
2019-10-24 11:20 ` Thomas, Rijo-john
2019-10-23 11:27 ` [RFC PATCH 5/5] crypto: ccp - provide in-kernel API to submit TEE commands Thomas, Rijo-john
2019-10-23 16:27 ` [RFC PATCH 0/5] Add TEE interface support to AMD Secure Processor driver Lendacky, Thomas
2019-10-24 11:21 ` Thomas, Rijo-john
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=e474bce6-8189-2c47-f61c-3c57532a43fd@amd.com \
--to=rijo-john.thomas@amd.com \
--cc=Devaraj.Rangasamy@amd.com \
--cc=Gary.Hook@amd.com \
--cc=Nimesh.Easow@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=ard.biesheuvel@linaro.org \
--cc=brijesh.singh@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®