Security Kconfig is not common
Subsystems (4)
Hi James,
Please help to review this patch.
When I analysis Kconfig files, I searched the keywork "source" and
then follow double quotations. The Kconfig in security is missing. That's because security/Kconfig source keyword didn't using double quotations.
Although that's may be not necessary. But I think the same as otherKconfig files will be better.
Best regards,
Winton.Liu
From ccd2d4ddc01076570f23d3f4bfa5b3845a71524e Mon Sep 17 00:00:00 2001
From: "winton.liu" <[email protected]>
Date: Wed, 23 Jan 2013 21:08:33 +0800
Subject: [PATCH] Security Kconfig not common
Add dobule quotations in Kconfig source keyword. That makes Kconfig files the same as other Kconfig. It's more common.
--- security/Kconfig | 12 ++++++------ security/integrity/Kconfig | 4 ++-- 2 files changed, 8 insertions(+), 8 deletions(-)
security/Kconfig +6 -6
@@ -183,13 +183,13 @@ config LSM_MMAP_MIN_ADDR this low address space will need the permission specific to the systems running LSM. -source security/selinux/Kconfig -source security/smack/Kconfig -source security/tomoyo/Kconfig -source security/apparmor/Kconfig -source security/yama/Kconfig +source "security/selinux/Kconfig" +source "security/smack/Kconfig" +source "security/tomoyo/Kconfig" +source "security/apparmor/Kconfig" +source "security/yama/Kconfig" -source security/integrity/Kconfig +source "security/integrity/Kconfig" choice prompt "Default security module"
security/integrity/Kconfig +2 -2
@@ -17,5 +17,5 @@ config INTEGRITY_SIGNATURE This is useful for evm and module keyrings, when keys are usually only added from initramfs. -source security/integrity/ima/Kconfig -source security/integrity/evm/Kconfig +source "security/integrity/ima/Kconfig" +source "security/integrity/evm/Kconfig"
Signature · 1 line
1.7.9.5
Quoted 10 lines · winton
Hi James,
Please help to review this patch.
When I analysisKconfigfiles, I searched the keywork "source" and
then follow double quotations. TheKconfigin security is missing. That's becausesecurity/Kconfigsource keyword didn't using double quotations.
Although that's may be not necessary. But I think the same as
otherKconfigfiles will be better.
Quoted 2 lines
Best regards,
Winton.Liu
The practice of quoting the source pathnames is usual, but far from universal. There are several examples in the arch and drivers directories. If you believe this is significant, see if the checkpatch maintainer is interested in adding a check.
Quoted 11 lines · Casey Schaufler
Quoted 10 lines · winton
Hi James,
Please help to review this patch.
When I analysisKconfigfiles, I searched the keywork "source" and
then follow double quotations. TheKconfigin security is missing. That's becausesecurity/Kconfigsource keyword didn't using double quotations.
Although that's may be not necessary. But I think the same as
otherKconfigfiles will be better.
Quoted 8 lines
Quoted 2 lines
Best regards,
Winton.LiuThe practice of quoting the source pathnames is usual, but far from universal. There are several examples in the arch and drivers directories. If you believe this is significant, see if the checkpatch maintainer is interested in adding a check.
Dear Casey,
Thank you for your explanations. Indeed that's now universal right now. That's the result I calculate (from the newest kenerl) :
Only 9 Kconfig doesn't contains quotations as belowing:./arch/cris/arch-v32/Kconfig ./arch/cris/arch-v32/drivers/Kconfig ./security/integrity/Kconfig./security/Kconfig./drivers/crypto/Kconfig./drivers/pps/Kconfig./drivers/hwmon/Kconfig./drivers/i2c/Kconfig./drivers/w1/Kconfig
There are 967 Kconfig in kernel
There are 159 Kconfig containning source keyword
I hope that would be universal one day. Just 9, not so much.
Best regards,
Winton.Liu