linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geert+renesas@glider.be (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/8] ASoC: sh: Update menu title and platform dependency
Date: Fri, 20 Apr 2018 15:28:32 +0200	[thread overview]
Message-ID: <1524230914-10175-7-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1524230914-10175-1-git-send-email-geert+renesas@glider.be>

Change the menu title to refer to "Renesas SoCs" instead of "SuperH", as
both SuperH and ARM SoCs are supported.

Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS")
is ARCH_RENESAS a more appropriate platform dependency for Renesas ARM
SoCs than the legacy ARCH_SHMOBILE, hence use the former.
Renesas SuperH SH-Mobile SoCs are still covered by the SUPERH
dependency.

This will allow to drop ARCH_SHMOBILE on ARM and ARM64 in the near
future.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
 sound/soc/sh/Kconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sound/soc/sh/Kconfig b/sound/soc/sh/Kconfig
index 1aa5cd77ca24a06f..c1b7fb91e3063f2b 100644
--- a/sound/soc/sh/Kconfig
+++ b/sound/soc/sh/Kconfig
@@ -1,5 +1,5 @@
-menu "SoC Audio support for SuperH"
-	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
+menu "SoC Audio support for Renesas SoCs"
+	depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
 
 config SND_SOC_PCM_SH7760
 	tristate "SoC Audio support for Renesas SH7760"
-- 
2.7.4

  parent reply	other threads:[~2018-04-20 13:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 13:28 [PATCH 0/8] arm: renesas: Change platform dependency to ARCH_RENESAS Geert Uytterhoeven
2018-04-20 13:28 ` [PATCH 1/8] arm: shmobile: " Geert Uytterhoeven
2018-04-20 14:53   ` Sergei Shtylyov
2018-04-23  7:50     ` Simon Horman
2018-04-20 13:28 ` [PATCH 2/8] dmaengine: shdmac: Change platform check to CONFIG_ARCH_RENESAS Geert Uytterhoeven
2018-04-23  7:53   ` Simon Horman
2018-04-25  9:18   ` Vinod Koul
2018-04-20 13:28 ` [PATCH 3/8] [media] v4l: rcar_fdp1: Change platform dependency to ARCH_RENESAS Geert Uytterhoeven
2018-04-21  8:07   ` Laurent Pinchart
2018-04-22  8:46     ` Laurent Pinchart
2018-04-23  8:08       ` Geert Uytterhoeven
2018-04-23  7:54   ` Simon Horman
2018-04-20 13:28 ` [PATCH 4/8] sh_eth: Change platform check to CONFIG_ARCH_RENESAS Geert Uytterhoeven
2018-04-20 15:22   ` Sergei Shtylyov
2018-04-23  7:56   ` Simon Horman
2018-04-20 13:28 ` [PATCH 5/8] staging: emxx_udc: Change platform dependency to ARCH_RENESAS Geert Uytterhoeven
2018-04-23  7:56   ` Simon Horman
2018-04-20 13:28 ` Geert Uytterhoeven [this message]
2018-04-23  7:56   ` [PATCH 6/8] ASoC: sh: Update menu title and platform dependency Simon Horman
2018-04-20 13:28 ` [PATCH/RFC 7/8] ARM: shmobile: Remove the ARCH_SHMOBILE Kconfig symbol Geert Uytterhoeven
2018-04-23  9:20   ` Simon Horman
2018-04-23  9:29   ` Simon Horman
2018-04-24  9:51   ` Geert Uytterhoeven
2018-04-20 13:28 ` [PATCH/RFC 8/8] arm64: renesas: " Geert Uytterhoeven
2018-04-20 13:40 ` [PATCH 0/8] arm: renesas: Change platform dependency to ARCH_RENESAS Arnd Bergmann
2018-04-20 16:48 ` Mark Brown
2018-04-23  7:45   ` Geert Uytterhoeven

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=1524230914-10175-7-git-send-email-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=linux-arm-kernel@lists.infradead.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 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).