All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	Kevin Hilman <khilman@kernel.org>,
	linux-clk@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH/RFC 0/2] clk / soc: renesas: Rework Kconfig and Makefile logic
Date: Wed, 26 Apr 2017 09:36:01 +0200	[thread overview]
Message-ID: <20170426073601.GF25517@verge.net.au> (raw)
In-Reply-To: <1493137626-21404-1-git-send-email-geert+renesas@glider.be>

On Tue, Apr 25, 2017 at 06:27:04PM +0200, Geert Uytterhoeven wrote:
> 	Hi all,
> 
> This RFC patch series reworks the Kconfig and Makefile logic for the
> Renesas clock and SoC drivers. It was sparked by a discussion with Olof
> about the Renesas clock driver dependencies.
> 
> The goals are to:
>   - Allow precise control over and automatic selection of which
>     (sub)drivers are used for which SoC (which may change in the
>     future),
>   - Allow adding support for new SoCs easily,
>   - Allow compile-testing of all (sub)drivers,
>   - Keep driver selection logic in the subsystem-specific Kconfig
>     independent from the architecture-specific Kconfig (i.e. no "select"
>     from arch/arm64/Kconfig.platforms), to avoid dependencies.
> 
> The series can't be applied as-is, because compile-testing all drivers
> depends on independent fixes, some in other subsystems.
> 
> More details are provided in the individual patch descriptions.
> 
> For testing, this patch series, plus several fixes to allow more
> compile-testing, are available in the
> topic/clk-soc-renesas-Kconfig-rework branch of my renesas-drivers git
> repository at 
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git.
> 
> This has been tested on R-Car Gen2 and Gen3, and compile-tested for
> various other configurations.
> 
> Thanks for your comments!

Hi Geert,

thanks for working on this. I am very pleased to see something that
is more robust with regards to adding new platforms without causing
build breakage - I have been burnt by this several times.

Acked-by: Simon Horman <horms+renesas@verge.net.au>

WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC 0/2] clk / soc: renesas: Rework Kconfig and Makefile logic
Date: Wed, 26 Apr 2017 09:36:01 +0200	[thread overview]
Message-ID: <20170426073601.GF25517@verge.net.au> (raw)
In-Reply-To: <1493137626-21404-1-git-send-email-geert+renesas@glider.be>

On Tue, Apr 25, 2017 at 06:27:04PM +0200, Geert Uytterhoeven wrote:
> 	Hi all,
> 
> This RFC patch series reworks the Kconfig and Makefile logic for the
> Renesas clock and SoC drivers. It was sparked by a discussion with Olof
> about the Renesas clock driver dependencies.
> 
> The goals are to:
>   - Allow precise control over and automatic selection of which
>     (sub)drivers are used for which SoC (which may change in the
>     future),
>   - Allow adding support for new SoCs easily,
>   - Allow compile-testing of all (sub)drivers,
>   - Keep driver selection logic in the subsystem-specific Kconfig
>     independent from the architecture-specific Kconfig (i.e. no "select"
>     from arch/arm64/Kconfig.platforms), to avoid dependencies.
> 
> The series can't be applied as-is, because compile-testing all drivers
> depends on independent fixes, some in other subsystems.
> 
> More details are provided in the individual patch descriptions.
> 
> For testing, this patch series, plus several fixes to allow more
> compile-testing, are available in the
> topic/clk-soc-renesas-Kconfig-rework branch of my renesas-drivers git
> repository at 
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git.
> 
> This has been tested on R-Car Gen2 and Gen3, and compile-tested for
> various other configurations.
> 
> Thanks for your comments!

Hi Geert,

thanks for working on this. I am very pleased to see something that
is more robust with regards to adding new platforms without causing
build breakage - I have been burnt by this several times.

Acked-by: Simon Horman <horms+renesas@verge.net.au>

  parent reply	other threads:[~2017-04-26  7:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 16:27 [PATCH/RFC 0/2] clk / soc: renesas: Rework Kconfig and Makefile logic Geert Uytterhoeven
2017-04-25 16:27 ` Geert Uytterhoeven
2017-04-25 16:27 ` [PATCH/RFC 1/2] clk: " Geert Uytterhoeven
2017-04-25 16:27   ` Geert Uytterhoeven
2017-05-19  1:17   ` Stephen Boyd
2017-05-19  1:17     ` Stephen Boyd
2017-04-25 16:27 ` [PATCH/RFC 2/2] soc: " Geert Uytterhoeven
2017-04-25 16:27   ` Geert Uytterhoeven
2017-04-26  7:36 ` Simon Horman [this message]
2017-04-26  7:36   ` [PATCH/RFC 0/2] clk / " 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=20170426073601.GF25517@verge.net.au \
    --to=horms@verge.net.au \
    --cc=arnd@arndb.de \
    --cc=geert+renesas@glider.be \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=olof@lixom.net \
    --cc=sboyd@codeaurora.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.