netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: [ANNOUNCE] iproute2 6.14.0 release
Date: Mon, 24 Mar 2025 09:23:19 -0700	[thread overview]
Message-ID: <20250324092319.28d39f2f@hermes.local> (raw)

This is small release of iproute2 corresponding to the 6.14 kernel.

Download:
    https://www.kernel.org/pub/linux/utils/net/iproute2/iproute2-6.14.0.tar.gz

Repository for current release
    https://github.com/shemminger/iproute2.git
    git://git.kernel.org/pub/scm/network/iproute2/iproute2.git

And future release (net-next):
    git://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git

Contributions:

David Ahern (3):
      Update kernel headers
      Update kernel headers
      Update kernel headers

Eric Dumazet (1):
      tc: fq: add support for TCA_FQ_OFFLOAD_HORIZON attribute

Ido Schimmel (2):
      ip: route: Add IPv6 flow label support
      iprule: Add flow label support

Matthieu Baerts (NGI0) (1):
      ss: mptcp: subflow: display seq counters as decimal

Michal Koutný (2):
      ss: Tone down cgroup path resolution
      README.devel: clarify patch rules and syntax

Petr Machata (1):
      ip: vxlan: Support IFLA_VXLAN_RESERVED_BITS

Robert Marko (1):
      ip: link: rmnet: add support for flag handling

Stephen Hemminger (2):
      uapi: update bpf.h
      v6.14.0

Torben Nielsen (2):
      tc: nat: Fix mask calculation
      tc: nat: ffs should operation on host byte ordered data

Xin Long (1):
      man: document tunnel options in ip-route.8.in

Yuyang Huang (2):
      iproute2: add 'ip monitor maddress' support
      iproute2: add 'ip monitor acaddress' support


                 reply	other threads:[~2025-03-24 16:23 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=20250324092319.28d39f2f@hermes.local \
    --to=stephen@networkplumber.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 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).