Re: [RFC PATCH 00/11] MIPS: OCTEON: move all octeon-ethernet code to staging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel




[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux