Re: [PATCH v2] sh_eth: Change platform check to CONFIG_ARCH_RENESAS

2018-05-18 Thread David Miller
From: Geert Uytterhoeven Date: Fri, 18 May 2018 12:52:51 +0200 > Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS") > is CONFIG_ARCH_RENESAS a more appropriate platform check than the legacy > CONFIG_ARCH_SHMOBILE, hence use the former. > > Renesas SuperH SH-Mobile SoCs are

Re: [PATCH v2] sh_eth: Change platform check to CONFIG_ARCH_RENESAS

2018-05-18 Thread Sergei Shtylyov
On 05/18/2018 01:52 PM, Geert Uytterhoeven wrote: > Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS") > is CONFIG_ARCH_RENESAS a more appropriate platform check than the legacy "If" should follow, not precede the option as this is not a question. :-) > CONFIG_ARCH_SHMOBIL

[PATCH v2] sh_eth: Change platform check to CONFIG_ARCH_RENESAS

2018-05-18 Thread Geert Uytterhoeven
Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS") is CONFIG_ARCH_RENESAS a more appropriate platform check than the legacy CONFIG_ARCH_SHMOBILE, hence use the former. Renesas SuperH SH-Mobile SoCs are still covered by the CONFIG_CPU_SH4 check. This will allow to drop ARCH_SH