Re: [PATCH] crypto: padlock-aes: constify x86_cpu_id

2017-09-22 Thread Herbert Xu
On Fri, Aug 25, 2017 at 11:53:42PM +0530, Arvind Yadav wrote:
> x86_cpu_id are not supposed to change at runtime. MODULE_DEVICE_TABLE
> and x86_match_cpu are working with const x86_cpu_id. So mark the
> non-const x86_cpu_id structs as const.
> 
> Signed-off-by: Arvind Yadav 

Patch applied.  Thanks.
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


[PATCH] crypto: padlock-aes: constify x86_cpu_id

2017-08-25 Thread Arvind Yadav
x86_cpu_id are not supposed to change at runtime. MODULE_DEVICE_TABLE
and x86_match_cpu are working with const x86_cpu_id. So mark the
non-const x86_cpu_id structs as const.

Signed-off-by: Arvind Yadav 
---
 drivers/crypto/padlock-aes.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/crypto/padlock-aes.c b/drivers/crypto/padlock-aes.c
index b386974..4b6642a 100644
--- a/drivers/crypto/padlock-aes.c
+++ b/drivers/crypto/padlock-aes.c
@@ -482,7 +482,7 @@ static struct crypto_alg cbc_aes_alg = {
}
 };
 
-static struct x86_cpu_id padlock_cpu_id[] = {
+static const struct x86_cpu_id padlock_cpu_id[] = {
X86_FEATURE_MATCH(X86_FEATURE_XCRYPT),
{}
 };
-- 
2.7.4