All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Vlad Dogaru <ddvlad@rosedu.org>, netdev@vger.kernel.org
Subject: Re: [PATCH v4 0/2] iproute2: support for device groups
Date: Wed, 2 Feb 2011 16:14:17 -0800	[thread overview]
Message-ID: <20110202161417.2a3d10a4@nehalam> (raw)
In-Reply-To: <4D49E252.1080006@trash.net>

On Thu, 03 Feb 2011 00:01:38 +0100
Patrick McHardy <kaber@trash.net> wrote:

> Am 02.02.2011 19:23, schrieb Vlad Dogaru:
> > This patch series adds userspace support for network device groups.
> > There is support for setting device groups, listing only interfaces of a
> > specific group, and setting basic device parameters for all interfaces
> > in a group.
> > 
> > Changes since version 3:
> >  * drop devgroup keyword. There is a single keyword for specifying
> >    groups now.
> >  * store group names internally as a hash, similar to routing table
> >    names. This is more efficient for batch mode operations
> 
> Looks good to me, thanks.

Will apply after 2.6.38 is released.

-- 

      reply	other threads:[~2011-02-03  0:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 18:23 [PATCH v4 0/2] iproute2: support for device groups Vlad Dogaru
2011-02-02 18:23 ` [PATCH v4 1/2] iproute2: support listing devices by group Vlad Dogaru
2011-02-25 20:43   ` Stephen Hemminger
2011-02-27  8:39     ` [PATCH nex-next] netdevice: make initial group visible to userspace Vlad Dogaru
2011-03-03  5:56       ` David Miller
2011-02-02 18:23 ` [PATCH v4 2/2] iproute2: support device group semantics Vlad Dogaru
2011-02-02 23:01 ` [PATCH v4 0/2] iproute2: support for device groups Patrick McHardy
2011-02-03  0:14   ` 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=20110202161417.2a3d10a4@nehalam \
    --to=shemminger@vyatta.com \
    --cc=ddvlad@rosedu.org \
    --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 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.