Re: [PATCH] MODSIGN: Fix including certificate twice when the signing_key.x509 already exists

Hi David, Thanks for your review and point out! 於 四，2013-02-21 於 14:16 +，David Howells 提到： > > +ifneq ($(shell pwd), $(srctree)) > > How reliable is this, I wonder? > > David > My current shell is bash, and I tried the '$(shell pwd)' in Makefile works for grab the REAL path when the

Re: [PATCH] MODSIGN: Fix including certificate twice when the signing_key.x509 already exists

Hi David, Thanks for your review and point out! 於 四，2013-02-21 於 14:16 +，David Howells 提到： +ifneq ($(shell pwd), $(srctree)) How reliable is this, I wonder? David My current shell is bash, and I tried the '$(shell pwd)' in Makefile works for grab the REAL path when the build path

Re: [PATCH] MODSIGN: Fix including certificate twice when the signing_key.x509 already exists

> +ifneq ($(shell pwd), $(srctree)) How reliable is this, I wonder? David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

[PATCH] MODSIGN: Fix including certificate twice when the signing_key.x509 already exists

This issue was found in devel-pekey branch on linux-modsign.git tree. The x509_certificate_list includes certificate twice when the signing_key.x509 already exists. We can reproduce this issue by making kernel twice, the build log of second time looks like this: ... CHK kernel/config_data.h

[PATCH] MODSIGN: Fix including certificate twice when the signing_key.x509 already exists

This issue was found in devel-pekey branch on linux-modsign.git tree. The x509_certificate_list includes certificate twice when the signing_key.x509 already exists. We can reproduce this issue by making kernel twice, the build log of second time looks like this: ... CHK kernel/config_data.h

Re: [PATCH] MODSIGN: Fix including certificate twice when the signing_key.x509 already exists

+ifneq ($(shell pwd), $(srctree)) How reliable is this, I wonder? David -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at