From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] VNIC: Adding support for Cavium ThunderX network controller
Date: Tue, 11 Nov 2014 13:39:21 -0500 (EST) [thread overview]
Message-ID: <20141111.133921.243613958949858000.davem@davemloft.net> (raw)
In-Reply-To: <1415596445-10061-1-git-send-email-rric@kernel.org>
From: Robert Richter <rric@kernel.org>
Date: Sun, 9 Nov 2014 21:14:05 -0800
> +config NET_VENDOR_CAVIUM
...
> +config THUNDER_NIC_PF
...
> +config THUNDER_NIC_VF
...
> +config THUNDER_NIC_BGX
These config options seem excessive, if not confusing. What would a
distribution be expected to enable? Everything?
> +# Don't change the order, NICPF driver is dependent on BGX driver init
> +obj-$(CONFIG_THUNDER_NIC_BGX) += thunder_bgx.o
> +obj-$(CONFIG_THUNDER_NIC_PF) += nicpf.o
> +obj-$(CONFIG_THUNDER_NIC_VF) += nicvf.o
Nothing ensures ordering if these things are built all modular.
Such ordering dependencies need to be resolved in another way.
next parent reply other threads:[~2014-11-11 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1415596445-10061-1-git-send-email-rric@kernel.org>
2014-11-11 18:39 ` David Miller [this message]
2014-11-12 14:52 ` [PATCH v2] VNIC: Adding support for Cavium ThunderX network controller Andrey Panin
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=20141111.133921.243613958949858000.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).