From: winton <newtonliuwen@gmail.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: james.l.morris@oracle.com, linux-security-module@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: Security Kconfig is not common
Date: Thu, 24 Jan 2013 18:26:46 +0800 [thread overview]
Message-ID: <51010C66.7080908@gmail.com> (raw)
In-Reply-To: <5100102A.6020009@schaufler-ca.com>
On 01/24/2013 12:30 AM, Casey Schaufler wrote:
> On 1/23/2013 5:28 AM, winton wrote:
>> 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
>> other Kconfig files will be better.
>>
>> 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.
>
>
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
prev parent reply other threads:[~2013-01-24 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 13:28 Security Kconfig is not common winton
2013-01-23 16:30 ` Casey Schaufler
2013-01-24 10:26 ` winton [this message]
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=51010C66.7080908@gmail.com \
--to=newtonliuwen@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-security-module@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