From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: Patrick McHardy <kaber@trash.net>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lartc@mailman.ds9a.nl
Subject: Re: [ANNOUNCE] iproute2 2.6.20-070313
Date: Wed, 14 Mar 2007 13:16:05 +0100 [thread overview]
Message-ID: <200703141316.05509.arekm@maven.pl> (raw)
In-Reply-To: <45F7E527.6030307@trash.net>
On Wednesday 14 of March 2007, Patrick McHardy wrote:
> Arkadiusz Miskiewicz wrote:
> > This patch
> >
> > http://www.mail-archive.com/netdev@vger.kernel.org/msg27506.html
> >
> > didn't make into upstream linux kernel it seems.
>
> As mentioned in the changelog, its in 2.6.19.
Hm, why no RTA_FWMASK in HEAD rtnetlink.h
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=include/linux/rtnetlink.h;h=4a629ea70cc4ca60a6f486f8653974af68dbe8cd;hb=HEAD
and 2.6.19
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=include/linux/rtnetlink.h;h=3a18addaed4ccb7436bffc9cf5fd0666f145d35c;hb=0215ffb08ce99e2bb59eca114a99499a4d06e704
?
> Last time I looked at the WRR patch it was a huge mess and
> used architecture dependant types in the netlink messages.
> Unless someone fixed this, adding support to iproute is a
> bad idea since in case it would get merged compatibility
> would break.
Ok.
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2007-03-14 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 22:15 [ANNOUNCE] iproute2 2.6.20-070313 Stephen Hemminger
2007-03-14 11:23 ` Arkadiusz Miskiewicz
2007-03-14 11:24 ` Arkadiusz Miskiewicz
2007-03-14 12:05 ` Patrick McHardy
2007-03-14 12:16 ` Arkadiusz Miskiewicz [this message]
2007-03-14 12:32 ` Patrick McHardy
2007-03-14 17:14 ` Stephen Hemminger
2007-03-14 20:42 ` Patrick McHardy
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=200703141316.05509.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=kaber@trash.net \
--cc=lartc@mailman.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).