Linux Power Management development
 help / color / mirror / Atom feed
From: Sumit Gupta <sumitg@nvidia.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rafael@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	zhongqiu.han@oss.qualcomm.com, conor+dt@kernel.org,
	treding@nvidia.com, jonathanh@nvidia.com,
	linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	bbasu@nvidia.com
Subject: Re: [PATCH v3 0/9] cpufreq: tegra194: add Tegra264 support
Date: Fri, 20 Nov 2026 13:06:56 +0530	[thread overview]
Message-ID: <61d207b2-3155-4613-bc9e-588c68f276fd@nvidia.com> (raw)
In-Reply-To: <av_R-8aMX7lL83ln@vireshk-B250M-D3H>

Hi Viresh,


On 20/11/26 10:22, Viresh Kumar wrote:
> External email: Use caution opening links or attachments
> 
> 
> On 19-11-26, 16:42, Sumit Gupta wrote:
>> This series adds cpufreq support for Tegra264, which joins the SoCs
>> already supported by the tegra194-cpufreq driver.
> 
> Please rebase over
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/arm/linux-next
> 
> The current series doesn't apply cleanly anymore.
> 
> --
> viresh

v3 was on linux-next, which has commit 4dd10fbbeb9c ("treewide: Convert
devm_kmalloc() family to the devm_kmalloc_obj() family") from v7.4-rc2.

Your branch seems to be on v7.4-rc1, so v4 on it would conflict with
that commit in mainline. Should I send v4 on your branch, or would you
prefer to move it to v7.4-rc2 or later first?

Best Regards,
Sumit Gupta


  reply	other threads:[~2026-11-20  7:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 11:12 [PATCH v3 0/9] cpufreq: tegra194: add Tegra264 support Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 1/9] cpufreq: tegra194: move MPIDR read to CPU hotplug callback Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 2/9] cpufreq: tegra194: remove duplicate counter sampling loops Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 3/9] cpufreq: tegra194: add tegra_counter_delta helper Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 4/9] cpufreq: tegra194: add per-SoC counter mask Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 5/9] cpufreq: tegra194: split MMIO mapping from ACTMON offset Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 6/9] dt-bindings: arm: nvidia: Document the Tegra264 CCPLEX cluster Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 7/9] cpufreq: tegra194: derive frequency domain from device tree Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 8/9] cpufreq: tegra194: Add support for Tegra264 Sumit Gupta
2026-11-19 11:12 ` [PATCH v3 9/9] arm64: tegra: Add CCPLEX cluster node " Sumit Gupta
2026-11-19 11:41 ` [PATCH v3 0/9] cpufreq: tegra194: add Tegra264 support Zhongqiu Han
2026-11-20  4:52 ` Viresh Kumar
2026-11-20  7:36   ` Sumit Gupta [this message]
2026-11-20  7:44     ` Viresh Kumar

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=61d207b2-3155-4613-bc9e-588c68f276fd@nvidia.com \
    --to=sumitg@nvidia.com \
    --cc=bbasu@nvidia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=treding@nvidia.com \
    --cc=viresh.kumar@linaro.org \
    --cc=zhongqiu.han@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox