[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150501205519.GA2550@kroah.com>
Date: Fri, 1 May 2015 22:55:19 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Aaro Koskinen <aaro.koskinen@....fi>
Cc: Ralf Baechle <ralf@...ux-mips.org>,
David Daney <ddaney.cavm@...il.com>,
David Daney <david.daney@...ium.com>,
devel@...verdev.osuosl.org, linux-mips@...ux-mips.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 00/11] MIPS: OCTEON: move all octeon-ethernet code to
staging
On Fri, May 01, 2015 at 10:37:02PM +0300, Aaro Koskinen wrote:
> Hi,
>
> In order to octeon-ethernet staging work to proceed, we should have all
> the code in the same tree (staging). Currently, most of the driver code
> actually lives in the MIPS tree in the "cvmx" helper or OS abstraction
> routines and include files. Majority of this code needs refactoring
> (or deletion) for the octeon-ethernet to become a normal Linux driver.
> Since rest of the kernel does not need this code at all, it should
> make sense to move it all into the same place while the driver
> is being developed.
>
> This series does not make any functional changes, just moves the code.
> Tested on EdgeRouter Lite, EdgeRouter Pro and D-Link DSR-1000N. Also build
> tested with octeon-ethernet as built-in, module and completely disabled.
> Patches are based on staging-next.
I don't object to this, especially if it helps get the octeon code out
of staging sooner.
But I need an ack from the MIPS maintainers before I can accept this into
the staging tree...
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists