From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 10/10] clk: Move HAVE_CLK config out of architecture layer
Date: Thu, 14 May 2020 12:57:50 -0700 [thread overview]
Message-ID: <158948627064.215346.9493279707055125868@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200409064416.83340-11-sboyd@kernel.org>
Quoting Stephen Boyd (2020-04-08 23:44:16)
> The implementation of 'struct clk' is not really an architectual detail
> anymore now that most architectures have migrated to the common clk
> framework. To sway new architecture ports away from trying to implement
> their own 'struct clk', move the config next to the common clk framework
> config.
>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> ---
Applied to clk-next
next prev parent reply other threads:[~2020-05-14 19:57 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 6:44 [PATCH v2 00/10] Allow COMMON_CLK to be selectable Stephen Boyd
2020-04-09 6:44 ` Stephen Boyd
2020-04-09 6:44 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 01/10] ARM: Remove redundant COMMON_CLK selects Stephen Boyd
2020-04-09 6:44 ` Stephen Boyd
2020-05-14 19:56 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 02/10] ARM: Remove redundant CLKDEV_LOOKUP selects Stephen Boyd
2020-04-09 6:44 ` Stephen Boyd
2020-05-14 19:56 ` Stephen Boyd
2020-05-14 19:56 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 03/10] arm64: tegra: " Stephen Boyd
2020-04-09 6:44 ` Stephen Boyd
2020-05-14 19:56 ` Stephen Boyd
2020-05-14 19:56 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 04/10] h8300: " Stephen Boyd
2020-05-14 19:56 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 05/10] MIPS: " Stephen Boyd
2020-05-14 19:56 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 06/10] mmc: meson-mx-sdio: Depend on OF_ADDRESS and not just OF Stephen Boyd
2020-04-21 14:04 ` Ulf Hansson
2020-04-22 10:14 ` Stephen Boyd
2020-04-22 10:39 ` Ulf Hansson
2020-05-14 19:57 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 07/10] clk: Allow the common clk framework to be selectable Stephen Boyd
2020-04-09 6:44 ` Stephen Boyd
2020-04-09 6:44 ` Stephen Boyd
2020-04-09 10:53 ` Mark Brown
2020-04-09 10:53 ` Mark Brown
2020-04-09 10:53 ` Mark Brown
2020-05-14 19:57 ` Stephen Boyd
2020-05-14 19:57 ` Stephen Boyd
2020-05-14 19:57 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 08/10] ARM: mmp: Remove legacy clk code Stephen Boyd
2020-04-09 6:44 ` Stephen Boyd
2020-05-14 19:57 ` Stephen Boyd
2020-05-14 19:57 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 09/10] MIPS: Loongson64: Drop asm/clock.h include Stephen Boyd
2020-05-14 19:57 ` Stephen Boyd
2020-04-09 6:44 ` [PATCH v2 10/10] clk: Move HAVE_CLK config out of architecture layer Stephen Boyd
2020-05-14 19:57 ` Stephen Boyd [this message]
2020-04-09 8:58 ` [PATCH v2 00/10] Allow COMMON_CLK to be selectable Arnd Bergmann
2020-04-09 8:58 ` Arnd Bergmann
2020-04-09 8:58 ` Arnd Bergmann
2020-04-09 9:02 ` [PATCH] mips: loongsoon2ef: remove private clk api Arnd Bergmann
2020-04-13 21:24 ` Philippe Mathieu-Daudé
2020-04-16 16:40 ` Thomas Bogendoerfer
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=158948627064.215346.9493279707055125868@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.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.