From: Patrick McHardy <kaber@trash.net>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lartc@mailman.ds9a.nl
Subject: [LARTC] Re: [ANNOUNCE] iproute2 2.6.20-070313
Date: Wed, 14 Mar 2007 12:05:59 +0000 [thread overview]
Message-ID: <45F7E527.6030307@trash.net> (raw)
In-Reply-To: <200703141223.48927.arekm@maven.pl>
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.
> The question is - are patches adding some functionality that's not in upstream
> kernel accepted?
>
> There is one wrr patch for iproute floating around that I'm thinking about.
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.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
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:05:59 +0100 [thread overview]
Message-ID: <45F7E527.6030307@trash.net> (raw)
In-Reply-To: <200703141223.48927.arekm@maven.pl>
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.
> The question is - are patches adding some functionality that's not in upstream
> kernel accepted?
>
> There is one wrr patch for iproute floating around that I'm thinking about.
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.
next prev parent reply other threads:[~2007-03-14 12:05 UTC|newest]
Thread overview: 12+ 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 [this message]
2007-03-14 12:05 ` Patrick McHardy
2007-03-14 12:16 ` Arkadiusz Miskiewicz
2007-03-14 12:32 ` [LARTC] " Patrick McHardy
2007-03-14 12:32 ` Patrick McHardy
2007-03-14 17:14 ` Stephen Hemminger
2007-03-14 20:42 ` [LARTC] " Patrick McHardy
2007-03-14 20:42 ` Patrick McHardy
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=45F7E527.6030307@trash.net \
--to=kaber@trash.net \
--cc=arekm@maven.pl \
--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 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.