From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Arnd Bergmann <arnd@arndb.de>,
Magnus Damm <magnus.damm@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] [RFC] arm64: renesas: Move SoC Kconfig symbols to drivers/soc/renesas/
Date: Wed, 17 Oct 2018 12:03:53 +0200 [thread overview]
Message-ID: <20181017100351.hisqesa3psw4pb5h@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWaXCu9KukLioxkcNoDQt4wKs2C9vrRbQRVJ+8+ux4PAQ@mail.gmail.com>
On Wed, Oct 17, 2018 at 11:56:43AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Oct 15, 2018 at 5:40 PM Simon Horman <horms@verge.net.au> wrote:
> > On Thu, Oct 11, 2018 at 03:54:55PM +0200, Simon Horman wrote:
> > > On Thu, Oct 11, 2018 at 10:55:07AM +0200, Geert Uytterhoeven wrote:
> > > > For consistency with other vendors, which have a single Kconfig symbol
> > > > in arch/arm64/Kconfig.platforms.
> > > >
> > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > > ---
> > > > Note that drivers/clk/ is included before drivers/soc/. Hence when
> > > > COMPILE_TEST=y, questions will be asked about clock drivers before they
> > > > can be auto-selected by SoC support.
> > > >
> > > > Question: Should we introduce a family-specific Kconfig symbol for R-Car
> > > > Gen3 (ARCH_RCAR_GEN1), which could be used for enabling
> > >
> > > s/1/3/?
>
> Sure.
>
> > > >
> > > > RST_RCAR?
> > >
> > > Given that it would be consistent with R-Car Gen 1 and 2,
> > > that seems like a good idea to me.
> >
> > there has been no other feedback on this series.
> > How would you like to proceed?
>
> I will add a new symbol ARCH_RCAR_GEN3 for v2?
Good plan.
> Any comments about PATCH 2/2?
Thanks, I have now commented.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] [RFC] arm64: renesas: Move SoC Kconfig symbols to drivers/soc/renesas/
Date: Wed, 17 Oct 2018 12:03:53 +0200 [thread overview]
Message-ID: <20181017100351.hisqesa3psw4pb5h@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWaXCu9KukLioxkcNoDQt4wKs2C9vrRbQRVJ+8+ux4PAQ@mail.gmail.com>
On Wed, Oct 17, 2018 at 11:56:43AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Oct 15, 2018 at 5:40 PM Simon Horman <horms@verge.net.au> wrote:
> > On Thu, Oct 11, 2018 at 03:54:55PM +0200, Simon Horman wrote:
> > > On Thu, Oct 11, 2018 at 10:55:07AM +0200, Geert Uytterhoeven wrote:
> > > > For consistency with other vendors, which have a single Kconfig symbol
> > > > in arch/arm64/Kconfig.platforms.
> > > >
> > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > > ---
> > > > Note that drivers/clk/ is included before drivers/soc/. Hence when
> > > > COMPILE_TEST=y, questions will be asked about clock drivers before they
> > > > can be auto-selected by SoC support.
> > > >
> > > > Question: Should we introduce a family-specific Kconfig symbol for R-Car
> > > > Gen3 (ARCH_RCAR_GEN1), which could be used for enabling
> > >
> > > s/1/3/?
>
> Sure.
>
> > > >
> > > > RST_RCAR?
> > >
> > > Given that it would be consistent with R-Car Gen 1 and 2,
> > > that seems like a good idea to me.
> >
> > there has been no other feedback on this series.
> > How would you like to proceed?
>
> I will add a new symbol ARCH_RCAR_GEN3 for v2?
Good plan.
> Any comments about PATCH 2/2?
Thanks, I have now commented.
next prev parent reply other threads:[~2018-10-17 17:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 8:55 [PATCH/RFC 0/2] arm: renesas: Move SoC Kconfig symbols to drivers/soc/renesas/ Geert Uytterhoeven
2018-10-11 8:55 ` Geert Uytterhoeven
2018-10-11 8:55 ` [PATCH 1/2] [RFC] arm64: " Geert Uytterhoeven
2018-10-11 8:55 ` Geert Uytterhoeven
2018-10-11 13:54 ` Simon Horman
2018-10-11 13:54 ` Simon Horman
2018-10-15 15:40 ` Simon Horman
2018-10-15 15:40 ` Simon Horman
2018-10-17 9:56 ` Geert Uytterhoeven
2018-10-17 9:56 ` Geert Uytterhoeven
2018-10-17 10:03 ` Simon Horman [this message]
2018-10-17 10:03 ` Simon Horman
2018-10-11 8:55 ` [PATCH 2/2] [RFC] ARM: shmobile: " Geert Uytterhoeven
2018-10-11 8:55 ` Geert Uytterhoeven
2018-10-17 10:03 ` Simon Horman
2018-10-17 10:03 ` Simon Horman
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=20181017100351.hisqesa3psw4pb5h@verge.net.au \
--to=horms@verge.net.au \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=will.deacon@arm.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 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.