linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Paul Cercueil <paul@crapouillou.net>,
	"H. Nikolaus Schaller" <hns@goldelico.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>
Subject: [PATCH v4 1/2] memory: jz4780-nemc: Do not build by default
Date: Tue, 28 Jul 2020 12:45:02 +0200	[thread overview]
Message-ID: <20200728104503.23655-1-krzk@kernel.org> (raw)

Enabling the JZ4780_NEMC driver makes sense only for specific hardware -
the Ingenic SoC architecture.  It is not an essential driver for the SoC
support so do not enable it by default.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>

---

Changes since v3:
1. Just drop the default, don't touch depends
2. Drop second patch for MTD_NAND_JZ4780

Changes since v2:
1. MIPS -> MACH_INGENIC, as suggested by Arnd
---
 drivers/memory/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/memory/Kconfig b/drivers/memory/Kconfig
index f64106fa63b7..8072204bc21a 100644
--- a/drivers/memory/Kconfig
+++ b/drivers/memory/Kconfig
@@ -164,7 +164,6 @@ config FSL_IFC
 
 config JZ4780_NEMC
 	bool "Ingenic JZ4780 SoC NEMC driver"
-	default y
 	depends on MIPS || COMPILE_TEST
 	depends on HAS_IOMEM && OF
 	help
-- 
2.17.1


             reply	other threads:[~2020-07-28 10:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 10:45 Krzysztof Kozlowski [this message]
2020-07-28 10:45 ` [PATCH v4 2/2] MIPS: ingenic: Enable JZ4780_NEMC manually Krzysztof Kozlowski
2020-07-28 11:12   ` Paul Cercueil
2020-07-28 11:19     ` Krzysztof Kozlowski
2020-07-28 11:37       ` Thomas Bogendoerfer
2020-07-28 12:00         ` Krzysztof Kozlowski
2020-07-28 12:33           ` Thomas Bogendoerfer
2020-07-28 12:51           ` Paul Cercueil
2020-07-28 12:53             ` Krzysztof Kozlowski
2020-07-28 20:51               ` Thomas Bogendoerfer
2020-07-28 11:36   ` Thomas Bogendoerfer

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=20200728104503.23655-1-krzk@kernel.org \
    --to=krzk@kernel.org \
    --cc=arnd@arndb.de \
    --cc=hns@goldelico.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=tsbogend@alpha.franken.de \
    /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).