From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
<Steen.Hegelund@microchip.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>
Subject: [PATCH v2 4/9] MIPS: mscc: Fix configuration name for ocelot legacy boards
Date: Tue, 10 Nov 2020 12:45:03 +0100 [thread overview]
Message-ID: <20201110114508.1197652-5-gregory.clement@bootlin.com> (raw)
In-Reply-To: <20201110114508.1197652-1-gregory.clement@bootlin.com>
Ocelots is supported by the generic MIPS build so make it clears that
LEGACY_BOARD_OCELOT is only needed for legacy boards which didn't have
bootloader supporting device tree.
Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
---
arch/mips/generic/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/generic/Kconfig b/arch/mips/generic/Kconfig
index 45431b88dded..eb2a3fa9fcd7 100644
--- a/arch/mips/generic/Kconfig
+++ b/arch/mips/generic/Kconfig
@@ -31,7 +31,7 @@ comment "MSCC Ocelot doesn't work with SEAD3 enabled"
depends on LEGACY_BOARD_SEAD3
config LEGACY_BOARD_OCELOT
- bool "Support MSCC Ocelot boards"
+ bool "Legacy support for Ocelot based boards"
depends on LEGACY_BOARD_SEAD3=n
select LEGACY_BOARDS
select SOC_VCOREIII
--
2.28.0
next prev parent reply other threads:[~2020-11-10 11:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 11:44 [PATCH v2 0/9] MIPS: Add support for more mscc SoCs: Luton, Serval and Jaguar2 Gregory CLEMENT
2020-11-10 11:45 ` [PATCH v2 1/9] dt-bindings: mips: Add Luton Gregory CLEMENT
2020-11-10 12:29 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 2/9] dt-bindings: mips: Add Serval and Jaguar2 Gregory CLEMENT
2020-11-10 12:30 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 3/9] MIPS: mscc: Prepare configuration to handle more SoCs Gregory CLEMENT
2020-11-10 12:30 ` Alexandre Belloni
2020-11-10 11:45 ` Gregory CLEMENT [this message]
2020-11-10 12:30 ` [PATCH v2 4/9] MIPS: mscc: Fix configuration name for ocelot legacy boards Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 5/9] MIPS: mscc: Add luton dtsi Gregory CLEMENT
2020-11-10 12:31 ` Alexandre Belloni
2020-11-10 12:32 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 6/9] MIPS: mscc: Add luton PC0B91 device tree Gregory CLEMENT
2020-11-10 12:33 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 7/9] MIPS: mscc: build FIT image for Luton Gregory CLEMENT
2020-11-10 12:33 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 8/9] MIPS: mscc: Add jaguar2 support Gregory CLEMENT
2020-11-10 12:33 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 9/9] MIPS: mscc: Add serval support Gregory CLEMENT
2020-11-10 12:34 ` Alexandre Belloni
2020-11-12 22:38 ` [PATCH v2 0/9] MIPS: Add support for more mscc SoCs: Luton, Serval and Jaguar2 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=20201110114508.1197652-5-gregory.clement@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--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).