From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms+renesas@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2] Input: sh_keysc - Remove dependency on SUPERH
Date: Fri, 04 Mar 2016 19:22:01 +0000 [thread overview]
Message-ID: <20160304192201.GC17145@dtor-ws> (raw)
In-Reply-To: <CAMuHMdWdeZkjk++5kpPLH6vHvz=ZAPqFp8z9od+Y-=R1W8HCxA@mail.gmail.com>
On Thu, Mar 03, 2016 at 09:11:18AM +0100, Geert Uytterhoeven wrote:
> On Thu, Mar 3, 2016 at 1:53 AM, Simon Horman <horms+renesas@verge.net.au> wrote:
> > A dependency on ARCH_SHMOBILE seems to be the best option for sh_keysc:
> >
> > * For Super H based SoCs: sh_keysc is used on SH_MIGOR, SH_ECOVEC, SH_KFR2R09,
> > SH_7722_SOLUTION_ENGINE, and SH_7724_SOLUTION_ENGINE, which depend on
> > either CPU_SUBTYPE_SH7722 or CPU_SUBTYPE_SH7724, and both select
> > ARCH_SHMOBILE.
> >
> > * For ARM Based SoCs: Since the removal of legacy (non-multiplatform) support
> > this driver has not been used by any Renesas ARM based SoCs. The Renesas
> > ARM based SoCs currently select ARCH_SHMOBILE, however, it is planned
> > that this will no longer be the case.
> >
> > This is part of an ongoing process to migrate from ARCH_SHMOBILE to
> > ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
> > appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
> >
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2016-03-04 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 0:53 [PATCH v2] Input: sh_keysc - Remove dependency on SUPERH Simon Horman
2016-03-03 8:11 ` Geert Uytterhoeven
2016-03-04 19:22 ` Dmitry Torokhov [this message]
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=20160304192201.GC17145@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-input@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).