All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org, linux-net@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] iproute2-2.6.33 version
Date: Wed, 24 Feb 2010 20:13:41 -0800	[thread overview]
Message-ID: <20100224201341.338dd71f@nehalam> (raw)

New version of iproute2 utilities that includes bug fixes and
support for all the new features in kernel 2.6.33. This integrates
a number of minor bug fixes from Debian as well.

Source: (note old developer.osdl.org address works as well)
	http://devresources.linux-foundation.org/dev/iproute2/download/iproute2-2.6.33.tar.bz2

Git tree:
	git://git.kernel.org/pub/scm/network/iproute2/iproute2.git

Changes since v.2.6.31:

Alex Badea (2):
      ip xfrm state: parse and print "icmp" and "af-unspec" flags
      ip xfrm policy: allow different tmpl family

Alexandre Cassen (1):
      IPv6: 6rd iproute2 support

Andreas Henriksson (2):
      iproute2: avoid using bashisms in configure script.
      iproute2: drop equalize support

Arnd Bergmann (1):
      iproute2/iplink: add macvlan options for bridge mode

Brian Haley (2):
      Add dadfailed option to ip command
      ip: print "temporary" for IPv6 temp addresses

Florian Westphal (5):
      tc: man: add limit parameter to tc-sfq man page
      tc: man: SO_PRIORITY is described in socket documentation, not tc one
      tc: red, gred, tbf: more helpful error messages
      tc: remove stale code
      tc: man: add man page for drr scheduler

Jamal Hadi Salim (1):
      skbedit: Add support to mark packets

Mike Frysinger (1):
      tc: respect LDFLAGS for %.so targets

Patrick McHardy (2):
      iplink_vlan: add support for VLAN loose binding flag
      iprule: add oif classification support

Stephen Hemminger (3):
      Update exported kernel headers
      iproute2-100205
      iproute2-10224


                 reply	other threads:[~2010-02-25  4:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100224201341.338dd71f@nehalam \
    --to=shemminger@vyatta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --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.