From: Shannon Nelson <shannon.nelson@oracle.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
netdev@vger.kernel.org, davem@davemloft.net
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 1/9] sunvnet: make sunvnet common code dynamically loadable
Date: Mon, 13 Feb 2017 09:16:08 -0800 [thread overview]
Message-ID: <cdc2ede8-5590-e8a2-00bf-d434bbe617a6@oracle.com> (raw)
In-Reply-To: <d4146a2e-2fc2-3c48-fedf-9f42b52800a0@cogentembedded.com>
On 2/12/2017 3:16 AM, Sergei Shtylyov wrote:
> Hello!
>
> On 2/10/2017 8:38 PM, Shannon Nelson wrote:
>
>> When the sunvnet_common code was split out for use by both sunvnet
>> and the newer ldmvsw, it was made into a static kernel library, which
>> limits the usefulness of sunvnet and ldmvsw as loadables, since most
>> of the real work is being done in the shared code. Also, this is
>> simply dead code in kernels that aren't running the LDoms.
>>
>> This patch makes the sunvnet_common into a dynamically loadable
>> module and makes sunvnet and ldmvsw dependent on sunvnet_common.
>>
>> Signed-off-by: Shannon Nelson <shannon.nelson@oracle.com>
>> ---
>> drivers/net/ethernet/sun/Kconfig | 8 ++++++--
>> drivers/net/ethernet/sun/sunvnet_common.c | 5 +++++
>> 2 files changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/sun/Kconfig
>> b/drivers/net/ethernet/sun/Kconfig
>> index a4b40e3..a7d91da 100644
>> --- a/drivers/net/ethernet/sun/Kconfig
>> +++ b/drivers/net/ethernet/sun/Kconfig
>> @@ -70,19 +70,23 @@ config CASSINI
>>
>> <http://docs.oracle.com/cd/E19113-01/giga.ether.pci/817-4341-10/817-4341-10.pdf>.
>>
>>
>> config SUNVNET_COMMON
>> - bool
>> + tristate "Common routines to support Sun Virtual Networking"
>> depends on SUN_LDOMS
>> - default y if SUN_LDOMS
>> + default m if SUN_LDOMS
>
> Sounds tautological... maybe just "default m"?
Yep, that can be tightened up.
Thanks,
sln
next prev parent reply other threads:[~2017-02-13 17:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 17:38 [PATCH v3 net-next 0/9] sunvnet driver updates Shannon Nelson
2017-02-10 17:38 ` [PATCH v3 net-next 1/9] sunvnet: make sunvnet common code dynamically loadable Shannon Nelson
2017-02-12 11:16 ` Sergei Shtylyov
2017-02-13 17:16 ` Shannon Nelson [this message]
2017-02-10 17:38 ` [PATCH v3 net-next 2/9] sunvnet: remove unused variable in maybe_tx_wakeup Shannon Nelson
2017-02-10 17:38 ` [PATCH v3 net-next 3/9] sunvnet: update version and version printing Shannon Nelson
2017-02-10 17:38 ` [PATCH v3 net-next 4/9] sunvnet: add driver stats for ethtool support Shannon Nelson
2017-02-11 0:22 ` Stephen Hemminger
2017-02-12 2:01 ` David Miller
2017-02-13 17:15 ` Shannon Nelson
2017-02-10 17:38 ` [PATCH v3 net-next 5/9] sunvnet: add memory barrier before check for tx enable Shannon Nelson
2017-02-10 17:38 ` [PATCH v3 net-next 6/9] sunvnet: straighten up message event handling logic Shannon Nelson
2017-02-10 17:38 ` [PATCH v3 net-next 7/9] sunvnet: remove extra rcu_read_unlocks Shannon Nelson
2017-02-10 17:38 ` [PATCH v3 net-next 8/9] ldmvsw: update and simplify version string Shannon Nelson
2017-02-10 17:38 ` [PATCH v3 net-next 9/9] ldmvsw: disable tso and gso for bridge operations Shannon Nelson
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=cdc2ede8-5590-e8a2-00bf-d434bbe617a6@oracle.com \
--to=shannon.nelson@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=sparclinux@vger.kernel.org \
/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
Powered by JetHome