From: Daniel Lezcano <dlezcano@fr.ibm.com>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: davem@davemloft.net, den@openvz.org, netdev@vger.kernel.org,
devel@openvz.org, containers@lists.osdl.org, xemul@openvz.org
Subject: Re: [PATCH 1/2 net-2.6.26] [NETNS]: Compilation fix for include/linux/netdevice.h.
Date: Wed, 26 Mar 2008 09:51:12 +0100 [thread overview]
Message-ID: <47EA0E80.2070302@fr.ibm.com> (raw)
In-Reply-To: <20080326.170702.24448643.yoshfuji@linux-ipv6.org>
YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <20080326.004742.92048899.davem@davemloft.net> (at Wed, 26 Mar 2008 00:47:42 -0700 (PDT)), David Miller <davem@davemloft.net> says:
>
>> From: "Denis V. Lunev" <den@openvz.org>
>> Date: Wed, 26 Mar 2008 10:40:58 +0300
>>
>>> Commit commit c346dca10840a874240c78efe3f39acf4312a1f2
>>> ([NET] NETNS: Omit net_device->nd_net without CONFIG_NET_NS)
>>> breaks compilation with CONFIG_NET_NS set.
>>>
>>> Fix the typo.
>>>
>>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> Applied.
>>
>> Too bad allmodconfig doesn't enable things which are y/n only.
>
> Sorry for the typo.
>
> Unfortunately, NET_NS depends on !SYSFS,
> so allyesconfig might not help...
Eric Biederman told us he has community acceptance for his approach and
he will push sysfs per namespace in a few weeks.
next prev parent reply other threads:[~2008-03-26 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 7:40 [PATCH 1/2 net-2.6.26] [NETNS]: Compilation fix for include/linux/netdevice.h Denis V. Lunev
2008-03-26 7:40 ` [PATCH 2/2 net-2.6.26] [NETNS]: Compilation warnings under CONFIG_NET_NS Denis V. Lunev
2008-03-26 7:48 ` David Miller
2008-03-26 7:47 ` [PATCH 1/2 net-2.6.26] [NETNS]: Compilation fix for include/linux/netdevice.h David Miller
2008-03-26 7:52 ` Denis V. Lunev
2008-03-26 8:07 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-26 8:51 ` Daniel Lezcano [this message]
2008-03-26 9:22 ` [Devel] " Alexey Dobriyan
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=47EA0E80.2070302@fr.ibm.com \
--to=dlezcano@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).