From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: leoyang.li@nxp.com
Cc: laurentiu.tudor@nxp.com, Roy.Pledge@nxp.com,
linux-kernel@vger.kernel.org,
Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: [PATCH 3/3] soc: fsl: FSL_MC_DPIO selects directly FSL_GUTS
Date: Wed, 3 Jul 2019 17:56:40 +0300 [thread overview]
Message-ID: <1562165800-30721-4-git-send-email-ioana.ciornei@nxp.com> (raw)
In-Reply-To: <1562165800-30721-1-git-send-email-ioana.ciornei@nxp.com>
Make FSL_MC_DPIO select directly FSL_GUTS. Without this change we could
be in a situation where both FSL_MC_DPIO and SOC_BUS are enabled but
FSL_GUTS is not.
Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
---
drivers/soc/fsl/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig
index b6804c04e96f..7e62c1d0aee7 100644
--- a/drivers/soc/fsl/Kconfig
+++ b/drivers/soc/fsl/Kconfig
@@ -22,7 +22,7 @@ config FSL_GUTS
config FSL_MC_DPIO
tristate "QorIQ DPAA2 DPIO driver"
depends on FSL_MC_BUS
- select SOC_BUS
+ select FSL_GUTS
help
Driver for the DPAA2 DPIO object. A DPIO provides queue and
buffer management facilities for software to interact with
--
1.9.1
next prev parent reply other threads:[~2019-07-03 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 14:56 [PATCH 0/3] soc: fsl: dpio: small fixes Ioana Ciornei
2019-07-03 14:56 ` [PATCH 1/3] bus: fsl-mc: remove explicit device_link_del Ioana Ciornei
2019-08-15 23:13 ` Li Yang
2019-08-16 6:02 ` Laurentiu Tudor
2019-08-16 19:54 ` Li Yang
2019-07-03 14:56 ` [PATCH 2/3] soc: fsl: dpio: remove explicit device_link_remove Ioana Ciornei
2019-08-15 23:17 ` Li Yang
2019-07-03 14:56 ` Ioana Ciornei [this message]
2019-08-15 23:09 ` [PATCH 3/3] soc: fsl: FSL_MC_DPIO selects directly FSL_GUTS Li Yang
2019-08-16 14:56 ` Roy Pledge
2019-08-16 17:03 ` Li Yang
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=1562165800-30721-4-git-send-email-ioana.ciornei@nxp.com \
--to=ioana.ciornei@nxp.com \
--cc=Roy.Pledge@nxp.com \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@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 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.