[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2dfaf36f-481d-82bf-79b6-2e7b80cfbe0e@canonical.com>
Date: Mon, 17 May 2021 07:32:14 -0400
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Thierry Reding <thierry.reding@...il.com>
Cc: Dmitry Osipenko <digetx@...il.com>, linux-kernel@...r.kernel.org,
Mikko Perttunen <mperttunen@...dia.com>,
linux-tegra@...r.kernel.org, linux-clk@...r.kernel.org,
Jonathan Hunter <jonathanh@...dia.com>,
Stephen Boyd <sboyd@...nel.org>,
Nathan Chancellor <nathan@...nel.org>
Subject: Re: [PATCH v2 0/4] Enable compile-testing of Tegra memory drivers
On 16/05/2021 12:12, Dmitry Osipenko wrote:
> This series enables compile-testing for all of NVIDIA Tegra memory
> drivers.
>
> Changelog:
>
> v2: - Added patch which should fix compilation warning of tegra124-emc driver
> on 64bit platforms that was reported by kernel build robot. Thanks
> to Nathan Chancellor for the suggested fix.
>
> memory: tegra124: Fix compilation warnings on 64bit platforms
>
> - Added missing stubs to the tegra-clk header in another new patch. This
> was also reported by kernel build robot for v1.
>
> clk: tegra: Add stubs needed for compile-testing
>
> - The memory/tegra/Kconfig now uses `if TEGRA_MC`, which was suggested
> by Krzysztof Kozlowski to v1. This makes Tegra Kconfig to look consistent
> with the Exynos Kconfig.
>
Hi Thierry,
The memory drivers part depends on soc and clk patches. There is also
another series from Dmitry (devm_tegra_core_dev_init_opp_table()) with
memory-soc dependency. I guess it makes sense you take everything via
soc-tegra, but just in case, can you keep the memory drivers on
dedicated branch?
Best regards,
Krzysztof
Powered by blists - more mailing lists