From: Mugunthan V N <mugunthanvnm@ti.com>
To: Murali Karicheri <m-karicheri2@ti.com>, <w-kwok2@ti.com>,
<davem@davemloft.net>, <tony@atomide.com>,
<prabhakar.csengg@gmail.com>, <grygorii.strashko@ti.com>,
<lokeshvutla@ti.com>, <mpa@pengutronix.de>,
<lsorense@csclub.uwaterloo.ca>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <arnd@arndb.de>
Subject: Re: [PATCH net-next] drivers: net: cpsw: make cpsw_ale.c a module to allow re-use on Keystone
Date: Fri, 30 Jan 2015 13:48:27 +0530 [thread overview]
Message-ID: <54CB3E53.8050307@ti.com> (raw)
In-Reply-To: <1422573351-5603-2-git-send-email-m-karicheri2@ti.com>
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@ti.com>
Acked-by: Mugunthan V N <mugunthanvnm@ti.com>
Will try to test this today/Monday.
Regards
Mugunthan V N
next prev parent reply other threads:[~2015-01-30 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 23:15 [PATCH net-next] netcp driver fixes to build as dynamic modules Murali Karicheri
2015-01-29 23:15 ` [PATCH net-next] drivers: net: cpsw: make cpsw_ale.c a module to allow re-use on Keystone Murali Karicheri
2015-01-29 23:47 ` Arnd Bergmann
2015-01-30 15:39 ` Murali Karicheri
2015-02-02 16:40 ` Tony Lindgren
2015-02-05 22:34 ` Murali Karicheri
2015-02-09 16:41 ` Tony Lindgren
2015-01-30 8:03 ` Lad, Prabhakar
2015-01-30 15:39 ` Murali Karicheri
2015-01-30 8:18 ` Mugunthan V N [this message]
2015-01-30 9:56 ` Mugunthan V N
2015-01-30 15:25 ` Murali Karicheri
2015-02-01 1:36 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54CB3E53.8050307@ti.com \
--to=mugunthanvnm@ti.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=m-karicheri2@ti.com \
--cc=mpa@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=tony@atomide.com \
--cc=w-kwok2@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.