netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Pavel Emelyanov <xemul@openvz.org>, netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] iproute2-2.6.23-rc3
Date: Sat, 1 Sep 2007 13:56:19 +0100	[thread overview]
Message-ID: <20070901135619.239b6d45@oldman> (raw)
In-Reply-To: <46D910E9.1040909@trash.net>

On Sat, 01 Sep 2007 09:12:41 +0200
Patrick McHardy <kaber@trash.net> wrote:

> Pavel Emelyanov wrote:
> > Patrick McHardy wrote:
> >> On Fri, 31 Aug 2007, Pavel Emelyanov wrote:
> >>
> >>>> Why does this add a new ip subcommand instead and uses genetlink
> >>>> instead of the rtnl_link API, which was introduced exactly for
> >>>> this stuff?
> >>>>
> >>> Hm... It does not, it just adds a parser for veth commands that
> >>> generic layer isn't aware of.
> >>
> >> It does, you have "ip veth add", "ip veth del", ...
> >>
> >> Didn't you already sent a patch that used "ip link add ..."?
> > 
> > The patch I sent last used "ip link add" and "ip link del".
> > The link_veth.c file only parses all the extra arguments.
> 
> 
> Thats what I thought. I seems Stephen applied an old version of
> the patch that still uses genetlink.
> 

Send me a new one, and I'll revert the old one.

      reply	other threads:[~2007-09-01 12:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 18:08 [ANNOUNCE] iproute2-2.6.23-rc3 Stephen Hemminger
2007-08-24 10:10 ` Jarek Poplawski
2007-08-24 19:26   ` Stephen Hemminger
2007-08-27  7:10     ` Jarek Poplawski
2007-08-31  9:10 ` Patrick McHardy
2007-08-31  9:15 ` Patrick McHardy
2007-08-31  9:34   ` Pavel Emelyanov
2007-08-31  9:45     ` Patrick McHardy
2007-08-31 11:42       ` Pavel Emelyanov
2007-09-01  7:12         ` Patrick McHardy
2007-09-01 12:56           ` Stephen Hemminger [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=20070901135619.239b6d45@oldman \
    --to=shemminger@linux-foundation.org \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=xemul@openvz.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).