From: Geert Uytterhoeven <geert+renesas@glider.be>
To: "David S . Miller" <davem@davemloft.net>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Solarflare linux maintainers <linux-net-drivers@solarflare.com>,
Edward Cree <ecree@solarflare.com>,
Bert Kenward <bkenward@solarflare.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 1/3] net: ethernet: Make NET_VENDOR_AURORA default to yes
Date: Wed, 4 Jul 2018 13:50:11 +0200 [thread overview]
Message-ID: <20180704115013.28078-2-geert+renesas@glider.be> (raw)
In-Reply-To: <20180704115013.28078-1-geert+renesas@glider.be>
Enabling NET_VENDOR_* Kconfig options does not directly affect the
kernel build. Hence NET_VENDOR_AURORA should default to yes, like other
NET_VENDOR_* options.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/net/ethernet/aurora/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/aurora/Kconfig b/drivers/net/ethernet/aurora/Kconfig
index 8ba7f8ff3434000f..392f564d8fd436f2 100644
--- a/drivers/net/ethernet/aurora/Kconfig
+++ b/drivers/net/ethernet/aurora/Kconfig
@@ -1,5 +1,6 @@
config NET_VENDOR_AURORA
bool "Aurora VLSI devices"
+ default y
help
If you have a network (Ethernet) device belonging to this class,
say Y.
--
2.17.1
next prev parent reply other threads:[~2018-07-04 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 11:50 [PATCH 0/3] net: ethernet: Miscellaneous Kconfig and Makefile cleanups Geert Uytterhoeven
2018-07-04 11:50 ` Geert Uytterhoeven [this message]
2018-07-04 11:50 ` [PATCH 2/3] net: ethernet: Add missing VENDOR to Cadence and Packet Engines symbols Geert Uytterhoeven
2018-07-04 11:50 ` [PATCH 3/3] net: ethernet: sfc: Make subdir logic consistent with other vendors Geert Uytterhoeven
2018-07-05 10:54 ` Martin Habets
2018-07-05 11:06 ` [PATCH 0/3] net: ethernet: Miscellaneous Kconfig and Makefile cleanups 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=20180704115013.28078-2-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=bkenward@solarflare.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.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