From: Casey Schaufler <casey@schaufler-ca.com>
To: David Miller <davem@davemloft.net>
Cc: rdunlap@xenotime.net, paul@paul-moore.com, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] Smack: Add missing depends on INET in Kconfig
Date: Fri, 30 Nov 2012 10:47:23 -0800 [thread overview]
Message-ID: <50B8FF3B.80003@schaufler-ca.com> (raw)
In-Reply-To: <20121130.134326.730429492162984746.davem@davemloft.net>
On 11/30/2012 10:43 AM, David Miller wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
> Date: Fri, 30 Nov 2012 09:40:09 -0800
>
>> On 11/30/2012 09:28 AM, Casey Schaufler wrote:
>>
>>> Because NETLABEL depends on INET SECURITY_SMACK
>>> has to explicitly call out the dependency.
>>>
>>> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
>>
>> Acked-by: Randy Dunlap <rdunlap@xenotime.net>
>>
>> Thanks for the quick fix.
> In what tree does this Kconfig file look like this?
James Morris' security-next
>
> In my net-next tree the current dependencies are expressed as:
>
> depends on NETLABEL && SECURITY_NETWORK
>
next prev parent reply other threads:[~2012-11-30 18:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 6:40 linux-next: Tree for Nov 29 Stephen Rothwell
2012-11-29 6:40 ` Stephen Rothwell
2012-11-29 23:43 ` [PATCH -next] of: export "allnodes" to fixx w1-gpio.c modular build Randy Dunlap
2012-11-30 9:54 ` Grant Likely
2012-11-30 0:05 ` linux-next: Tree for Nov 29 (netlabel) Randy Dunlap
2012-11-30 15:19 ` Paul Moore
2012-11-30 15:31 ` Paul Moore
2012-11-30 16:55 ` Randy Dunlap
2012-11-30 17:22 ` Casey Schaufler
2012-11-30 17:28 ` [PATCH] Smack: Add missing depends on INET in Kconfig Casey Schaufler
2012-11-30 17:40 ` Randy Dunlap
2012-11-30 18:43 ` David Miller
2012-11-30 18:47 ` Casey Schaufler [this message]
2012-11-30 18:43 ` Paul Moore
2012-11-30 22:01 ` Eric Paris
2012-11-30 22:18 ` Casey Schaufler
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=50B8FF3B.80003@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.