From: thirtythreeforty@gmail.com
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: George Hilliard <thirtythreeforty@gmail.com>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
NeilBrown <neil@brown.name>
Subject: [PATCH v2 2/2] Mediatek staging: Use individual config flags in Makefile
Date: Thu, 10 Jan 2019 17:43:37 -0700 [thread overview]
Message-ID: <20190111004337.7223-2-thirtythreeforty@gmail.com> (raw)
In-Reply-To: <20190111004337.7223-1-thirtythreeforty@gmail.com>
From: George Hilliard <thirtythreeforty@gmail.com>
These drivers are useful on other MT76xx SoCs, which have compatible
peripherals. The drivers are selectable in Kconfig, but they were
quietly excluded from the build because the SOC_MT7621 chip was not
selected. So, make the main staging Makefile use the same flags as
everything else for these drivers.
mt7621-dma and mt7621-dts are left alone because they truly do require
that SoC.
I have personally confirmed that the mt7621-spi driver works on the
MT7688, which was what prompted this change.
Cc: linux-kernel@vger.kernel.org
Cc: devel@driverdev.osuosl.org
Cc: NeilBrown <neil@brown.name>
Signed-off-by: George Hilliard <thirtythreeforty@gmail.com>
---
drivers/staging/Makefile | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/Makefile b/drivers/staging/Makefile
index e095f427177c..4b78ea2c7848 100644
--- a/drivers/staging/Makefile
+++ b/drivers/staging/Makefile
@@ -42,12 +42,12 @@ obj-$(CONFIG_BCM2835_VCHIQ) += vc04_services/
obj-$(CONFIG_DRM_VBOXVIDEO) += vboxvideo/
obj-$(CONFIG_PI433) += pi433/
obj-$(CONFIG_SOC_MT7621) += mt7621-pci/
-obj-$(CONFIG_SOC_MT7621) += mt7621-pinctrl/
-obj-$(CONFIG_SOC_MT7621) += mt7621-spi/
+obj-$(CONFIG_PINCTRL_RT2880) += mt7621-pinctrl/
+obj-$(CONFIG_SPI_MT7621) += mt7621-spi/
obj-$(CONFIG_SOC_MT7621) += mt7621-dma/
-obj-$(CONFIG_SOC_MT7621) += ralink-gdma/
-obj-$(CONFIG_SOC_MT7621) += mt7621-mmc/
-obj-$(CONFIG_SOC_MT7621) += mt7621-eth/
+obj-$(CONFIG_DMA_RALINK) += ralink-gdma/
+obj-$(CONFIG_MTK_MMC) += mt7621-mmc/
+obj-$(CONFIG_NET_MEDIATEK_SOC_STAGING) += mt7621-eth/
obj-$(CONFIG_SOC_MT7621) += mt7621-dts/
obj-$(CONFIG_STAGING_GASKET_FRAMEWORK) += gasket/
obj-$(CONFIG_XIL_AXIS_FIFO) += axis-fifo/
--
2.20.1
next prev parent reply other threads:[~2019-01-11 0:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACmrr9gHucWaWtz07kQms6AsquLKAHbK+_Q0kF=92RGo6HmAFA@mail.gmail.com>
2019-01-11 0:43 ` [PATCH v2 1/2] Move ralink-gdma to its own directory thirtythreeforty
2019-01-11 0:43 ` thirtythreeforty [this message]
2019-01-15 15:30 ` [PATCH v2 2/2] staging: Mediatek: Use individual config flags in Makefile Greg Kroah-Hartman
2019-01-15 17:02 ` [PATCH v3] " George Hilliard
2019-01-15 17:20 ` Greg Kroah-Hartman
2019-01-15 17:29 ` [PATCH v4] " George Hilliard
2019-01-15 17:43 ` Greg Kroah-Hartman
2019-01-16 6:48 ` [PATCH v5] " George Hilliard
2019-01-16 4:43 ` [PATCH v4] " kbuild test robot
2019-01-15 17:32 ` [PATCH v3] " George Hilliard
2019-01-11 1:21 ` [PATCH v2 1/2] Move ralink-gdma to its own directory NeilBrown
2019-01-11 2:13 ` George Hilliard
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=20190111004337.7223-2-thirtythreeforty@gmail.com \
--to=thirtythreeforty@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
/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.