lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 30 Jan 2015 15:26:32 +0530 From: Mugunthan V N <mugunthanvnm@...com> To: Murali Karicheri <m-karicheri2@...com>, <w-kwok2@...com>, <davem@...emloft.net>, <tony@...mide.com>, <prabhakar.csengg@...il.com>, <grygorii.strashko@...com>, <lokeshvutla@...com>, <mpa@...gutronix.de>, <lsorense@...lub.uwaterloo.ca>, <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>, <arnd@...db.de> Subject: Re: [PATCH net-next] drivers: net: cpsw: make cpsw_ale.c a module to allow re-use on Keystone On Friday 30 January 2015 01:48 PM, Mugunthan V N wrote: > On Friday 30 January 2015 04:45 AM, Murali Karicheri wrote: >> NetCP on Keystone has cpsw ale function similar to other TI SoCs >> and this driver is re-used. To allow both ti cpsw and keystone netcp >> to re-use the driver, convert the cpsw ale to a module and configure >> it through Kconfig option CONFIG_TI_CPSW_ALE. Currently it is statically >> linked to both TI CPSW and NetCP and this causes issues when the above >> drivers are built as dynamic modules. This patch addresses this issue >> >> While at it, fix the Makefile and code to build both netcp_core and >> netcp_ethss as dynamic modules. This is needed to support arm allmodconfig. >> This also requires exporting of API calls provided by netcp_core so that >> both the above can be dynamic modules. >> >> Signed-off-by: Murali Karicheri <m-karicheri2@...com> > > Acked-by: Mugunthan V N <mugunthanvnm@...com> > > Will try to test this today/Monday. > > I have tested this on DRA7 platform and passed tested ping. Tested-by: Mugunthan V N <mugunthanvnm@...com> Regards Mugunthan V N -- 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