From: Pavel Emelianov <xemul@openvz.org>
To: Patrick McHardy <kaber@trash.net>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Linux Netdev List <netdev@vger.kernel.org>,
Linux Containers <containers@lists.osdl.org>,
Kirill Korotaev <dev@openvz.org>
Subject: Re: [PATCH] Virtual ethernet tunnel
Date: Wed, 13 Jun 2007 20:02:22 +0400 [thread overview]
Message-ID: <4670150E.5010309@openvz.org> (raw)
In-Reply-To: <466FD113.3070909@trash.net>
Patrick McHardy wrote:
> Pavel Emelianov wrote:
>> Patrick McHardy wrote:
>>
>>> The question is how to proceed. I haven't read all mails yet, but it
>>> seems there is some disagreement about whether to create all devices
>>> in the same namespace and move them later or create them directly in
>>
>> The agreement was that we can make any of the above. We can create
>> booth devices in the init namespace and then move one of them into the
>> desired namespace, or we can explicitly specify which namespace to create
>> the pair in.
>
>
> I'm going to push my latest patches to Dave today, the easiest way is
> probably is you just add whatever you need to the API afterwards.
>
>
OK. Dave didn't object against the driver. Hope he will accept it as well.
I have also found a BUG in your API. Look, when you declare the alias with
the MODULE_ALIAS_RTNL_LINK in drivers you use strings as an argument. But
this macro stringifyes the argument itself which results in bad aliases.
Signed-off-by: Pavel Emelianov <xemul@openvz.org>
---
diff --git a/include/net/rtnetlink.h b/include/net/rtnetlink.h
index d744198..f627e1f 100644
--- a/include/net/rtnetlink.h
+++ b/include/net/rtnetlink.h
@@ -77,6 +77,6 @@ extern void __rtnl_link_unregister(struc
extern int rtnl_link_register(struct rtnl_link_ops *ops);
extern void rtnl_link_unregister(struct rtnl_link_ops *ops);
-#define MODULE_ALIAS_RTNL_LINK(name) MODULE_ALIAS("rtnl-link-" #name)
+#define MODULE_ALIAS_RTNL_LINK(name) MODULE_ALIAS("rtnl-link-" name)
#endif
next prev parent reply other threads:[~2007-06-13 15:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 15:11 [PATCH] Virtual ethernet tunnel Pavel Emelianov
2007-06-06 15:17 ` [PATCH] Module for ip utility to support veth device Pavel Emelianov
2007-06-06 15:18 ` Patrick McHardy
2007-06-06 15:28 ` [PATCH] Virtual ethernet tunnel Patrick McHardy
2007-06-07 8:09 ` Pavel Emelianov
2007-06-07 9:29 ` Daniel Lezcano
2007-06-07 9:51 ` Pavel Emelianov
2007-06-07 14:05 ` Daniel Lezcano
2007-06-07 14:23 ` Kirill Korotaev
2007-06-07 14:42 ` Daniel Lezcano
2007-06-07 15:33 ` Pavel Emelianov
2007-06-07 15:25 ` Pavel Emelianov
2007-06-07 15:44 ` Daniel Lezcano
2007-06-11 11:39 ` Patrick McHardy
2007-06-13 9:24 ` Pavel Emelianov
2007-06-13 11:12 ` Patrick McHardy
2007-06-13 16:02 ` Pavel Emelianov [this message]
2007-06-13 15:37 ` Patrick McHardy
2007-06-06 15:39 ` Patrick McHardy
2007-06-06 16:17 ` Stephen Hemminger
2007-06-06 19:47 ` David Miller
2007-06-06 20:38 ` [Devel] " Daniel Lezcano
2007-06-06 20:49 ` David Miller
2007-06-07 8:14 ` Kirill Korotaev
2007-06-07 9:07 ` David Miller
2007-06-07 9:30 ` Benjamin Thery
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=4670150E.5010309@openvz.org \
--to=xemul@openvz.org \
--cc=containers@lists.osdl.org \
--cc=dev@openvz.org \
--cc=ebiederm@xmission.com \
--cc=kaber@trash.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).