From: Stephen Hemminger <stephen@networkplumber.org>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, David Miller <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Sandeep Nair <sandeep_n@ti.com>
Subject: Re: [PATCH 0/2] net: Add Keystone NetCP ethernet driver support
Date: Tue, 22 Apr 2014 15:02:31 -0700 [thread overview]
Message-ID: <20140422150231.2e87b7eb@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1398201675-17379-1-git-send-email-santosh.shilimkar@ti.com>
On Tue, 22 Apr 2014 17:21:13 -0400
Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
> NetCP driver has a plug-in module architecture where each of the NetCP
> sub-modules exist as a loadable kernel module which plug in to the netcp
> core. These sub-modules are represented as "netcp-devices" in the dts
> bindings. It is mandatory to have the ethernet switch sub-module for
> the ethernet interface to be operational. Any other sub-module like the
> PA is optional.
Where is the implementation of these modules. You need to include
this as separate patch set. Also the hooks for these modules should all
be EXPORT_SYMBOL_GPL() to disallow proprietary modules.
next prev parent reply other threads:[~2014-04-22 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 21:21 [PATCH 0/2] net: Add Keystone NetCP ethernet driver support Santosh Shilimkar
2014-04-22 21:21 ` [PATCH 1/2] Documentation: dt: net: Add binding doc for Keystone NetCP ethernet driver Santosh Shilimkar
2014-04-22 21:21 ` [PATCH 2/2] net: Add " Santosh Shilimkar
2014-04-24 16:47 ` David Miller
2014-04-24 21:04 ` Santosh Shilimkar
2014-04-22 22:02 ` Stephen Hemminger [this message]
2014-04-22 23:56 ` [PATCH 0/2] net: Add Keystone NetCP ethernet driver support Santosh Shilimkar
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=20140422150231.2e87b7eb@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sandeep_n@ti.com \
--cc=santosh.shilimkar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox