From: "Jorge Boncompte [DTI2]" <jorge@dti2•net>
To: shemminger@vyatta•com
Cc: igorm@etf•rs, Linux Network Development list <netdev@vger•kernel.org>
Subject: Re: MPLS for Linux kernel
Date: Mon, 21 Nov 2011 18:46:20 +0100 [thread overview]
Message-ID: <4ECA8E6C.5020701@dti2.net> (raw)
In-Reply-To: <20111121091711.1be69369@nehalam.linuxnetplumber.net>
El 21/11/2011 18:17, Stephen Hemminger escribió:
> On Mon, 21 Nov 2011 16:01:26 +0100
> "Jorge Boncompte [DTI2]" <jorge@dti2•net> wrote:
>
>> El 20/11/2011 22:59, Igor Maravić escribió:
>>> Hi all,
>>> I've been working on implementation of MPLS for Linux kernel, for a
>>> some time now.
>>> I continued the work of James Leu
>>> (https://sourceforge.net/projects/mpls-linux/) and used some fixes of
>>> Jorge Boncompte
>>> (http://mpls-linux.git.sourceforge.net/git/gitweb.cgi?p=mpls-linux/net-next;a=shortlog;h=refs/heads/net-next-mpls).
>>>
>>> I fixed a lot of bugs, so now it can be compiled and run with all
>>> Kernel Hacking options enabled.
>>> My code could be found on this sites:
>>>
>>> https://github.com/i-maravic/MPLS-Linux
>>> https://github.com/i-maravic/iproute2
>>>
>>> Any feedback is appreciated :)
>>
>> Provide, clean, separated, and commented changes to the upstream project as we
>> have asked you several times to do.
>>
>> mpls-linux it is not ready to go upstream in my opinion.
>
> Out of tree is out of mind. Very few developers will bother with
> a kernel component not in the mainline tree.
Yes, I am well aware of it. I've been cleaning the code, as time permits, with
the intention of trying to submit it.
>
> Staging?
I have not really looked at it but I thought that staging is only for drivers?
The mpls-linux code has some (little) hooks in the core networking stuff but I
think that maybe we can remove them and make it almost stand alone.
I would be more than happy to move the code out of the shadows.
--
==============================================================
Jorge Boncompte - Ingenieria y Gestion de RED
DTI2 - Desarrollo de la Tecnologia de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5 14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
==============================================================
- There is only so much duct tape you can put on something
before it just becomes a giant ball of duct tape.
==============================================================
next prev parent reply other threads:[~2011-11-21 17:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 21:59 MPLS for Linux kernel Igor Maravić
2011-11-21 15:01 ` Jorge Boncompte [DTI2]
2011-11-21 17:17 ` Stephen Hemminger
2011-11-21 17:46 ` Jorge Boncompte [DTI2] [this message]
2011-11-21 18:29 ` David Miller
2011-11-21 19:18 ` Jorge Boncompte [DTI2]
2011-11-22 8:52 ` Igor Maravić
2011-11-22 12:30 ` Jorge Boncompte [DTI2]
2011-11-22 13:55 ` Igor Maravić
2011-11-22 14:33 ` Jorge Boncompte [DTI2]
2011-11-22 14:35 ` Jorge Boncompte [DTI2]
2011-11-22 15:51 ` Igor Maravić
2011-11-22 21:41 ` Igor Maravić
2011-11-22 21:49 ` David Miller
2011-11-23 7:09 ` Igor Maravić
2011-11-24 23:39 ` Glen Turner
2011-11-25 5:43 ` David Miller
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=4ECA8E6C.5020701@dti2.net \
--to=jorge@dti2$(echo .)net \
--cc=igorm@etf$(echo .)rs \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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