All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>, linux-rockchip@lists.infradead.org
Cc: kernel@esmil.dk, linux-clk@vger.kernel.org,
	mturquette@baylibre.com, heiko@sntech.de
Subject: Re: [PATCH 2/2] clk: rockchip: drop module parts from rk3399 and rk3568 drivers
Date: Thu, 28 Oct 2021 23:42:47 -0700	[thread overview]
Message-ID: <163548976724.15791.12515100208357999661@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20211027132616.1039814-3-heiko@sntech.de>

Quoting Heiko Stuebner (2021-10-27 06:26:16)
> Both of these drivers were converted to real drivers and got a tristate
> build option. But them being builtin_platform_drivers, they only ever
> should be build-in - as the name suggests.
> 
> So adapt the Kconfig symbol and drop the MODULE_* parts from the drivers.
> 
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---

Reviewed-by: Stephen Boyd <sboyd@kernel.org>

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>, linux-rockchip@lists.infradead.org
Cc: kernel@esmil.dk, linux-clk@vger.kernel.org,
	mturquette@baylibre.com, heiko@sntech.de
Subject: Re: [PATCH 2/2] clk: rockchip: drop module parts from rk3399 and rk3568 drivers
Date: Thu, 28 Oct 2021 23:42:47 -0700	[thread overview]
Message-ID: <163548976724.15791.12515100208357999661@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20211027132616.1039814-3-heiko@sntech.de>

Quoting Heiko Stuebner (2021-10-27 06:26:16)
> Both of these drivers were converted to real drivers and got a tristate
> build option. But them being builtin_platform_drivers, they only ever
> should be build-in - as the name suggests.
> 
> So adapt the Kconfig symbol and drop the MODULE_* parts from the drivers.
> 
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---

Reviewed-by: Stephen Boyd <sboyd@kernel.org>

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2021-10-29  6:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 13:26 [PATCH 0/2] clk: rockchip: cleanup errors in (module-)driver handling Heiko Stuebner
2021-10-27 13:26 ` Heiko Stuebner
2021-10-27 13:26 ` [PATCH 1/2] Revert "clk: rockchip: use module_platform_driver_probe" Heiko Stuebner
2021-10-27 13:26   ` Heiko Stuebner
2021-10-29  6:42   ` Stephen Boyd
2021-10-29  6:42     ` Stephen Boyd
2021-10-27 13:26 ` [PATCH 2/2] clk: rockchip: drop module parts from rk3399 and rk3568 drivers Heiko Stuebner
2021-10-27 13:26   ` Heiko Stuebner
2021-10-29  6:42   ` Stephen Boyd [this message]
2021-10-29  6:42     ` Stephen Boyd
2021-10-27 20:27 ` [PATCH 0/2] clk: rockchip: cleanup errors in (module-)driver handling Stephen Boyd
2021-10-27 20:27   ` Stephen Boyd
2021-10-27 23:20   ` Heiko Stübner
2021-10-27 23:20     ` Heiko Stübner
2021-10-29  6:43     ` Stephen Boyd
2021-10-29  6:43       ` Stephen Boyd
2021-10-29 12:37       ` Heiko Stübner
2021-10-29 12:37         ` Heiko Stübner
2021-11-03  0:59         ` Stephen Boyd
2021-11-03  0:59           ` Stephen Boyd

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=163548976724.15791.12515100208357999661@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@esmil.dk \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --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.