From: Dirk Behme <dirk.behme@de.bosch.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v8 01/07] arm64: renesas: r8a7795: Add Renesas R8A7795 SoC support
Date: Thu, 03 Sep 2015 07:13:10 +0000 [thread overview]
Message-ID: <55E7F306.2080802@de.bosch.com> (raw)
In-Reply-To: <20150831062918.24004.15458.sendpatchset@little-apple>
On 03.09.2015 09:04, Laurent Pinchart wrote:
> Hi Geert,
>
> On Monday 31 August 2015 15:38:40 Geert Uytterhoeven wrote:
>> On Mon, Aug 31, 2015 at 12:44 PM, Laurent Pinchart wrote:
>>> On Monday 31 August 2015 15:29:18 Magnus Damm wrote:
>>>> --- 0001/arch/arm64/Kconfig.platforms
>>>> +++ work/arch/arm64/Kconfig.platforms 2015-08-29 18:20:52.022366518 +0900
>>>> @@ -66,6 +66,22 @@ config ARCH_SEATTLE
>>>> help
>>>> This enables support for AMD Seattle SOC Family
>>>>
>>>> +config ARCH_SHMOBILE
>>>> + bool
>>>
>>> It's tempting to get rid of ARCH_SHMOBILE going forward and define
>>> ARCH_RENESAS on ARM32 instead. I'm not sure whether that's worth it, even
>>> though the change would just be a search & replace.
>>
>> What's the meaning of "ARCH_RENESAS"?
>> Does that include H8/300, m32r, and SuperH, too?
>>
>> I know "SH Mobile" has been used for both SuperH and ARM32, but it's
>> still closer ;-)
>
> Let's postpone that until arch/h8300 and arch/m32r become deprecated then ;-)
>
> It's still a bit annoying not to have a proper name to describe SuperH, ARM32
> and ARM64 SoCs that share the same Renesas IP cores.
Btw, for patches starting with the subject "arm64: ..." wouldn't it make
sense to at least CC linux-arm-kernel?
Best regards
Dirk
next prev parent reply other threads:[~2015-09-03 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 6:29 [PATCH v8 01/07] arm64: renesas: r8a7795: Add Renesas R8A7795 SoC support Magnus Damm
2015-08-31 9:07 ` Geert Uytterhoeven
2015-08-31 10:44 ` Laurent Pinchart
2015-08-31 13:38 ` Geert Uytterhoeven
2015-09-03 7:04 ` Laurent Pinchart
2015-09-03 7:13 ` Dirk Behme [this message]
2015-09-03 7:24 ` Magnus Damm
2015-09-03 7:59 ` Magnus Damm
2015-09-08 20:36 ` Laurent Pinchart
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=55E7F306.2080802@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=linux-sh@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.