From: Olof Johansson <olof@lixom.net>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Will Deacon <will@kernel.org>
Subject: Re: [GIT PULL] memory: Tegra for v5.14, part two
Date: Tue, 15 Jun 2021 08:41:55 -0700 [thread overview]
Message-ID: <20210615154155.GE11724@lx2k> (raw)
In-Reply-To: <20210614195200.21657-1-krzysztof.kozlowski@canonical.com>
Hi,
On Mon, Jun 14, 2021 at 09:52:00PM +0200, Krzysztof Kozlowski wrote:
> Hi Arnd and Olof,
>
> Tegra got quite big rework this cycle. The last piece comes from Thierry,
> however it depends on one patch in Will's tree. Since the last Thierry's
> patches depend both on that one patch and other memory controller drivers
> changes, they are here.
>
> Best regards,
> Krzysztof
So, this pull request is a bit weird. It contains a lot more than what the
email indicates:
> The following changes since commit 393d66fd2cacba3e6aa95d7bb38790bfb7b1cc3a:
>
> memory: tegra: Implement SID override programming (2021-06-03 21:50:43 +0200)
This seems to be a patch in the middle of the new material in your branch, not
the start of what we already have in our tree.
As a result, the diffstat when we merge looks completely different. While
I generally trust you to not try to squeeze in material under the radar, it's
also unfortunately making it hard to double-check that you didn't accidentally
bring in something you didn't mean to.
So, before I merge this.. can you confirm, or even better generate a full pull
request summary/diffstat/pull request email that shows the full new material?
Thanks!
-Olof
next prev parent reply other threads:[~2021-06-15 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 19:52 [GIT PULL] memory: Tegra for v5.14, part two Krzysztof Kozlowski
2021-06-15 15:41 ` Olof Johansson [this message]
2021-06-16 7:20 ` Krzysztof Kozlowski
2021-06-17 0:35 ` Olof Johansson
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=20210615154155.GE11724@lx2k \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--cc=treding@nvidia.com \
--cc=will@kernel.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