From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754631Ab3CXTGs (ORCPT ); Sun, 24 Mar 2013 15:06:48 -0400 Received: from mail.active-venture.com ([67.228.131.205]:53458 "EHLO mail.active-venture.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754309Ab3CXTGq (ORCPT ); Sun, 24 Mar 2013 15:06:46 -0400 X-Originating-IP: 108.223.40.66 Date: Sun, 24 Mar 2013 12:06:53 -0700 From: Guenter Roeck To: Ben Collins Cc: David Miller , afleming@freescale.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH] net: Add support for handling queueing in hardware Message-ID: <20130324190653.GA16227@roeck-us.net> References: <20130322.101139.1942128058226201237.davem@davemloft.net> <20130322.103302.1277256650283142022.davem@davemloft.net> <20130323190221.GA22005@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130323190221.GA22005@roeck-us.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 23, 2013 at 12:02:21PM -0700, Guenter Roeck wrote: > On Fri, Mar 22, 2013 at 10:43:44AM -0400, Ben Collins wrote: > > On Mar 22, 2013, at 10:33 AM, David Miller wrote: > > > > > From: Fleming Andy-AFLEMING > > > Date: Fri, 22 Mar 2013 14:31:50 +0000 > > > > > >> It would appear one of our customers is attempting to upstream our > > >> code for us. We are aware that this current solution is unacceptable > > >> (which is why we have not submitted it), and we are currently trying > > >> to develop a less hacky solution that integrates with qdisc. > > > > > > Ben, can can you coordinate with people instead of doing crap like > > > this? > > > > > > "For us" is a loose term, when it's more that we are attempting to upstream code so our system is supported by a mainline kernel instead of having one-off kernels. > > > > And we have been talking with Freescale about this for quite some time (couple years?). They have a roadmap that doesn't include getting this driver supported in mainline any time soon, so I'm taking time to get this done for our own system. I'm not meaning to step on any toes. > > > How true. You are not the only one with thatt problem. > > Ben, can you possibly send me your complete patch set on top of 3.8, or point me > to a git tree ? > Never mind, I found your tree on github. I'll clone it next week and start playing with it. That is going to save me a lot of time. Thanks a lot for the work! Our system is based on P5040, and I might be able to do some testing on P5020 as well. I'll let you know how it goes. Thanks, Guenter