Re: Gigabit ethernet driver for Alacritechs SLIC devices (v4)
On 06.12.2016 17:30, David Miller wrote: > From: Lino Sanfilippo> Date: Mon, 5 Dec 2016 23:07:15 +0100 > >> this is the forth version of the slicoss gigabit ethernet driver (which is a >> rework of the driver from Alacritech which can currently be found under >> drivers/staging/slicoss). The driver is supposed to support Mojave, Oasis and >> Kalahari cards, for both copper and fiber. >> >> If this code is accepted the staging version can be removed. >> >> The driver has been tested on a SEN2104ET adapter (4 Port PCIe copper). > > I've applied this series, nice work. > Great, thanks! Regards, Lino ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: Gigabit ethernet driver for Alacritechs SLIC devices (v4)
From: Greg KHDate: Tue, 6 Dec 2016 17:40:39 +0100 > On Tue, Dec 06, 2016 at 11:30:04AM -0500, David Miller wrote: >> From: Lino Sanfilippo >> Date: Mon, 5 Dec 2016 23:07:15 +0100 >> >> > this is the forth version of the slicoss gigabit ethernet driver (which is >> > a >> > rework of the driver from Alacritech which can currently be found under >> > drivers/staging/slicoss). The driver is supposed to support Mojave, Oasis >> > and >> > Kalahari cards, for both copper and fiber. >> > >> > If this code is accepted the staging version can be removed. >> > >> > The driver has been tested on a SEN2104ET adapter (4 Port PCIe copper). >> >> I've applied this series, nice work. >> >> But realize that if you use SLICOSS as the Kconfig symbol to select >> this driver, then while the staging driver is still in the tree it >> will enable both drivers which both want to attach to the same exact >> device IDs. > > If you have taken this in your tree now, I will go delete the staging > driver from the staging tree, so we will not have that issue. Should I > do that now? Please do. ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: Gigabit ethernet driver for Alacritechs SLIC devices (v4)
On Tue, Dec 06, 2016 at 11:30:04AM -0500, David Miller wrote: > From: Lino Sanfilippo> Date: Mon, 5 Dec 2016 23:07:15 +0100 > > > this is the forth version of the slicoss gigabit ethernet driver (which is a > > rework of the driver from Alacritech which can currently be found under > > drivers/staging/slicoss). The driver is supposed to support Mojave, Oasis > > and > > Kalahari cards, for both copper and fiber. > > > > If this code is accepted the staging version can be removed. > > > > The driver has been tested on a SEN2104ET adapter (4 Port PCIe copper). > > I've applied this series, nice work. > > But realize that if you use SLICOSS as the Kconfig symbol to select > this driver, then while the staging driver is still in the tree it > will enable both drivers which both want to attach to the same exact > device IDs. If you have taken this in your tree now, I will go delete the staging driver from the staging tree, so we will not have that issue. Should I do that now? thanks, greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: Gigabit ethernet driver for Alacritechs SLIC devices (v4)
From: Lino SanfilippoDate: Mon, 5 Dec 2016 23:07:15 +0100 > this is the forth version of the slicoss gigabit ethernet driver (which is a > rework of the driver from Alacritech which can currently be found under > drivers/staging/slicoss). The driver is supposed to support Mojave, Oasis and > Kalahari cards, for both copper and fiber. > > If this code is accepted the staging version can be removed. > > The driver has been tested on a SEN2104ET adapter (4 Port PCIe copper). I've applied this series, nice work. But realize that if you use SLICOSS as the Kconfig symbol to select this driver, then while the staging driver is still in the tree it will enable both drivers which both want to attach to the same exact device IDs. ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel