From: Thierry Reding <thierry.reding@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Sumit Gupta <sumitg@nvidia.com>,
treding@nvidia.com, dmitry.osipenko@collabora.com,
viresh.kumar@linaro.org, rafael@kernel.org, jonathanh@nvidia.com,
robh+dt@kernel.org, lpieralisi@kernel.org, helgaas@kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-pci@vger.kernel.org, mmaddireddy@nvidia.com, kw@linux.com,
bhelgaas@google.com, vidyas@nvidia.com, sanjayc@nvidia.com,
ksitaraman@nvidia.com, ishah@nvidia.com, bbasu@nvidia.com
Subject: Re: [Patch v8 0/8] Tegra234 Memory interconnect support
Date: Mon, 15 May 2023 18:18:38 +0200 [thread overview]
Message-ID: <ZGJbXg88JOu4aiNe@orome> (raw)
In-Reply-To: <a032d9e6-6cb5-1856-9eda-28028bf05633@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
On Sun, May 14, 2023 at 12:41:45PM +0200, Krzysztof Kozlowski wrote:
> On 11/05/2023 19:32, Sumit Gupta wrote:
> > Hi All,
> >
> > Have incorporated the suggestions in v7. Only changed 'patch 1' in v7
> > to fix possible race when setting 'mc->bpmp' as pointed by Krzysztof.
> > Requesting to merge the patch series.
> >
>
> Can I apply it since you request it? I asked you long time ago to
> clearly state dependencies or merging limitations. It's v8 and cover
> letter still does not state it. Neither the patches do.
I thought we had discussed and agreed to merge this through the Tegra
tree, which is why you had provided Acked-bys on all the patches. I was
waiting for a final Acked-by on patch 1, since that was the only one
still being revised.
If you prefer to merge this, that works for me too. In that case, the
series:
Acked-by: Thierry Reding <treding@nvidia.com>
Although it might be good if I pick up at least patch 8, just as a
precautionary measure to avoid potential conflicts going forward. As I
understand, it should be safe to apply that separately.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-15 16:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 17:32 [Patch v8 0/8] Tegra234 Memory interconnect support Sumit Gupta
2023-05-11 17:32 ` [Patch v8 1/8] memory: tegra: add interconnect support for DRAM scaling in Tegra234 Sumit Gupta
2023-05-16 7:42 ` Krzysztof Kozlowski
2023-05-11 17:32 ` [Patch v8 2/8] memory: tegra: add mc clients for Tegra234 Sumit Gupta
2023-05-11 17:32 ` [Patch v8 3/8] memory: tegra: add software mc clients in Tegra234 Sumit Gupta
2023-05-11 17:32 ` [Patch v8 4/8] dt-bindings: tegra: add icc ids for dummy MC clients Sumit Gupta
2023-05-11 17:32 ` [Patch v8 5/8] memory: tegra: make cpu cluster bw request a multiple of mc channels Sumit Gupta
2023-05-11 17:32 ` [Patch v8 6/8] PCI: tegra194: Fix possible array out of bounds access Sumit Gupta
2023-05-11 17:32 ` [Patch v8 7/8] PCI: tegra194: Add interconnect support in Tegra234 Sumit Gupta
2023-05-11 17:32 ` [Patch v8 8/8] arm64: tegra: Add cpu OPP tables and interconnects property Sumit Gupta
2023-05-14 10:41 ` [Patch v8 0/8] Tegra234 Memory interconnect support Krzysztof Kozlowski
2023-05-15 10:57 ` Sumit Gupta
2023-05-15 16:18 ` Thierry Reding [this message]
2023-05-16 7:42 ` Krzysztof Kozlowski
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=ZGJbXg88JOu4aiNe@orome \
--to=thierry.reding@gmail.com \
--cc=bbasu@nvidia.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=helgaas@kernel.org \
--cc=ishah@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=ksitaraman@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sanjayc@nvidia.com \
--cc=sumitg@nvidia.com \
--cc=treding@nvidia.com \
--cc=vidyas@nvidia.com \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).