[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53341A63.3000004@mojatatu.com>
Date: Thu, 27 Mar 2014 08:32:35 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Thomas Graf <tgraf@...g.ch>
CC: Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org,
davem@...emloft.net, nhorman@...driver.com, andy@...yhouse.net,
dborkman@...hat.com, ogerlitz@...lanox.com, jesse@...ira.com,
pshelar@...ira.com, azhou@...ira.com, ben@...adent.org.uk,
stephen@...workplumber.org, jeffrey.t.kirsher@...el.com,
vyasevic@...hat.com, xiyou.wangcong@...il.com,
john.r.fastabend@...el.com, edumazet@...gle.com,
sfeldma@...ulusnetworks.com, f.fainelli@...il.com,
roopa@...ulusnetworks.com, linville@...driver.com,
dev@...nvswitch.org
Subject: Re: [patch net-next RFC v2 0/6] introduce infrastructure for support
of switch chip datapath
On 03/27/14 08:00, Thomas Graf wrote:
> It seems like we reached pretty good consensus on the model. What
> remaining issues do you see with the port model proposed in v2?
>
Are we really following the same thread?
I dont see any rallying behind Jiri's approach from the
other folks who have their own code and way of approaching things.
I am hoping we dont continue with the split that is there
already.
cheers,
jamal
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists