Message ID | 20171004131412.13038-10-brijesh.singh@amd.com (mailing list archive) |
---|---|
State | Not Applicable |
Delegated to: | Herbert Xu |
Headers | show |
On Wed, Oct 04, 2017 at 08:13:50AM -0500, Brijesh Singh wrote: > From: Borislav Petkov <bp@suse.de> > > This is AMD-specific hardware so present it in Kconfig only when AMD > CPU support is enabled or on ARM64 where it is also used. > > Signed-off-by: <brijesh.singh@amd.com> > Signed-off-by: Borislav Petkov <bp@suse.de> For the future, when you carry a patch from someone else, your SOB should come after the author's. I.e., Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> i.e., the first SOB is the author's and the second is yours which means, you've handled the patch further on, like sending it upstream, for example. Thx.
On 10/04/2017 04:47 PM, Borislav Petkov wrote:> > Signed-off-by: Borislav Petkov <bp@suse.de> > Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> > > i.e., the first SOB is the author's and the second is yours which means, > you've handled the patch further on, like sending it upstream, for > example. > Noted, thanks
diff --git a/drivers/crypto/ccp/Kconfig b/drivers/crypto/ccp/Kconfig index 6d626606b9c5..9c84f9838931 100644 --- a/drivers/crypto/ccp/Kconfig +++ b/drivers/crypto/ccp/Kconfig @@ -1,5 +1,6 @@ config CRYPTO_DEV_CCP_DD tristate "Secure Processor device driver" + depends on CPU_SUP_AMD || ARM64 default m help Provides AMD Secure Processor device driver.