From: Thierry Reding <thierry.reding@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm-soc <arm@kernel.org>, SoC Team <soc@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
"open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-clk <linux-clk@vger.kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: [GIT PULL 07/11] memory: tegra: Changes for v5.8-rc1
Date: Tue, 26 May 2020 13:40:54 +0200 [thread overview]
Message-ID: <20200526114054.GA2935745@ulmo> (raw)
In-Reply-To: <CAK8P3a0kqjt8UNxe2ruRDOJNedOcqWxP-i5y2uW6YsaMNJgejg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
On Mon, May 25, 2020 at 11:52:30PM +0200, Arnd Bergmann wrote:
> On Fri, May 15, 2020 at 4:53 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> >
> > ----------------------------------------------------------------
> > memory: tegra: Changes for v5.8-rc1
> >
> > Contains a few cleanup patches and an implementation to scale the EMC
> > frequency on Tegra210 systems.
>
> I don't mind taking the memory driver patches, but it seems odd that this
> pull request has so many drivers/clk changes but does not mention that
> in the pull request, and does not Cc the clk maintainers or include Acks
> from them.
>
> I would assume that the reason for this is that you have based
> the memory controller changes on a branch that was already
> accepted by the clk maintainers in to their tree, but when you do that
> please be more explicit so I know what is going on.
So historically there's often a lot of dependencies, either build-time
or runtime, between Tegra clock patches and other work. That's why we
ended up with this model where I collect Tegra clock patches in the
Tegra tree and it's not uncommon to end up with the clock branch being
a dependency of one of the other branches.
I did send this to Mike and Stephen about 1 1/2 weeks ago, but it does
not look like they've pulled it into the clk tree yet.
I typically highlight the dependencies in the pull request, but looks
like I forgot to do that this time around.
> Waiting for clarification before I can pull this.
Given the above, might be best to hold off on this for a bit until the
clock branch was pulled by Mike or Stephen.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Jon Hunter <jonathanh@nvidia.com>, SoC Team <soc@kernel.org>,
arm-soc <arm@kernel.org>,
"open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 07/11] memory: tegra: Changes for v5.8-rc1
Date: Tue, 26 May 2020 13:40:54 +0200 [thread overview]
Message-ID: <20200526114054.GA2935745@ulmo> (raw)
In-Reply-To: <CAK8P3a0kqjt8UNxe2ruRDOJNedOcqWxP-i5y2uW6YsaMNJgejg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1652 bytes --]
On Mon, May 25, 2020 at 11:52:30PM +0200, Arnd Bergmann wrote:
> On Fri, May 15, 2020 at 4:53 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> >
> > ----------------------------------------------------------------
> > memory: tegra: Changes for v5.8-rc1
> >
> > Contains a few cleanup patches and an implementation to scale the EMC
> > frequency on Tegra210 systems.
>
> I don't mind taking the memory driver patches, but it seems odd that this
> pull request has so many drivers/clk changes but does not mention that
> in the pull request, and does not Cc the clk maintainers or include Acks
> from them.
>
> I would assume that the reason for this is that you have based
> the memory controller changes on a branch that was already
> accepted by the clk maintainers in to their tree, but when you do that
> please be more explicit so I know what is going on.
So historically there's often a lot of dependencies, either build-time
or runtime, between Tegra clock patches and other work. That's why we
ended up with this model where I collect Tegra clock patches in the
Tegra tree and it's not uncommon to end up with the clock branch being
a dependency of one of the other branches.
I did send this to Mike and Stephen about 1 1/2 weeks ago, but it does
not look like they've pulled it into the clk tree yet.
I typically highlight the dependencies in the pull request, but looks
like I forgot to do that this time around.
> Waiting for clarification before I can pull this.
Given the above, might be best to hold off on this for a bit until the
clock branch was pulled by Mike or Stephen.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-26 11:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 14:53 [GIT PULL 00/11] tegra: Changes for v5.8-rc1 Thierry Reding
2020-05-15 14:53 ` Thierry Reding
[not found] ` <20200515145311.1580134-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-05-15 14:53 ` [GIT PULL 01/11] cpufreq: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 02/11] cpuidle: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 03/11] dt-bindings: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 04/11] of: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 05/11] firmware: tegra: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
[not found] ` <20200515145311.1580134-6-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-05-22 14:28 ` [GIT PULL v2 " Thierry Reding
2020-05-22 14:28 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 06/11] media: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 07/11] memory: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
2020-05-25 21:52 ` Arnd Bergmann
2020-05-25 21:52 ` Arnd Bergmann
2020-05-25 21:52 ` Arnd Bergmann
2020-05-26 11:40 ` Thierry Reding [this message]
2020-05-26 11:40 ` Thierry Reding
2020-05-26 22:12 ` Stephen Boyd
2020-05-26 22:12 ` Stephen Boyd
2020-06-15 14:02 ` Thierry Reding
2020-06-15 14:02 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 08/11] soc/tegra: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
[not found] ` <20200515145311.1580134-9-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-05-22 14:28 ` [GIT PULL v2 " Thierry Reding
2020-05-22 14:28 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 09/11] ARM: tegra: Core changes " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 10/11] ARM: tegra: Device tree " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
2020-05-15 14:53 ` [GIT PULL 11/11] arm64: " Thierry Reding
2020-05-15 14:53 ` Thierry Reding
[not found] ` <20200515145311.1580134-12-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-05-20 13:43 ` Thierry Reding
2020-05-20 13:43 ` Thierry Reding
2020-05-22 14:28 ` [GIT PULL v2 " Thierry Reding
2020-05-22 14:28 ` Thierry Reding
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=20200526114054.GA2935745@ulmo \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=soc@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 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.