From: ebiederm@xmission.com (Eric W. Biederman)
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: Support specifying the network namespace upon device creation.
Date: Tue, 03 Nov 2009 01:50:23 -0800 [thread overview]
Message-ID: <m1ws28ey3k.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4AEFF7BB.4090301@gmail.com> (Eric Dumazet's message of "Tue\, 03 Nov 2009 10\:28\:27 +0100")
Eric Dumazet <eric.dumazet@gmail.com> writes:
>
> Very nice, with only one long line you could wrap differently.
Say again? Was that very nice with respect to the rest of the patch?
Or sarcasm because I overlooked this wrap at 80 columns
opportunity in ipgre?
Eric
>
>> -static int ipgre_newlink(struct net_device *dev, struct nlattr *tb[],
>> +static int ipgre_newlink(struct net *src_net, struct net_device *dev, struct nlattr *tb[],
>> struct nlattr *data[])
>> {
>> struct ip_tunnel *nt;
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-03 9:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 9:03 [PATCH] net: Support specifying the network namespace upon device creation Eric W. Biederman
2009-11-03 9:28 ` Eric Dumazet
2009-11-03 9:50 ` Eric W. Biederman [this message]
2009-11-03 9:56 ` Eric Dumazet
2009-11-03 10:06 ` Eric W. Biederman
2009-11-03 10:05 ` David Miller
2009-11-03 10:16 ` Eric Dumazet
2009-11-03 10:44 ` David Miller
2009-11-03 13:26 ` [PATCH net-next-2.6] net: cleanup include/net Eric Dumazet
2009-11-04 13:07 ` David Miller
2009-11-04 17:48 ` [PATCH net-next-2.6] net: cleanup include/linux Eric Dumazet
2009-11-04 17:51 ` David Miller
2009-11-03 10:32 ` [PATCH] net: Support specifying the network namespace upon device creation Eric W. Biederman
2009-11-08 8:54 ` David Miller
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=m1ws28ey3k.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).