From: Arnd Bergmann <arnd@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
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>
Subject: Re: [GIT PULL 5/6] arm64: tegra: Device tree changes for v5.11-rc1
Date: Fri, 27 Nov 2020 20:44:51 +0100 [thread overview]
Message-ID: <CAK8P3a2vcd0QgfwjTTPM1gk=tTqD+n-4ww-vhJQ3M0z_AZMyDQ@mail.gmail.com> (raw)
In-Reply-To: <20201127144329.124891-5-thierry.reding@gmail.com>
On Fri, Nov 27, 2020 at 3:43 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> Note that you've already pulled part of this earlier as fixes for
> v5.10-rc6, but I've included the whole lot for completeness. Let me know
> if that doesn't work for you and you'd rather have a completely separate
> branch.
The way you did it works best in my opinion, as it helps with bisectability
and it avoids the backmerge of a later -rc into an existing branch.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>, SoC Team <soc@kernel.org>,
arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL 5/6] arm64: tegra: Device tree changes for v5.11-rc1
Date: Fri, 27 Nov 2020 20:44:51 +0100 [thread overview]
Message-ID: <CAK8P3a2vcd0QgfwjTTPM1gk=tTqD+n-4ww-vhJQ3M0z_AZMyDQ@mail.gmail.com> (raw)
Message-ID: <20201127194451.z82kLYAuRz4MWDQ2ZSlRS9EV2yCj-Siu-O85RPowY8c@z> (raw)
In-Reply-To: <20201127144329.124891-5-thierry.reding@gmail.com>
On Fri, Nov 27, 2020 at 3:43 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> Note that you've already pulled part of this earlier as fixes for
> v5.10-rc6, but I've included the whole lot for completeness. Let me know
> if that doesn't work for you and you'd rather have a completely separate
> branch.
The way you did it works best in my opinion, as it helps with bisectability
and it avoids the backmerge of a later -rc into an existing branch.
Arnd
_______________________________________________
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-11-27 19:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 14:43 [GIT PULL 1/6] dt-bindings: Changes for v5.11-rc1 Thierry Reding
2020-11-27 14:43 ` Thierry Reding
2020-11-27 14:43 ` [GIT PULL 2/6] soc/tegra: " Thierry Reding
2020-11-27 14:43 ` Thierry Reding
2020-11-27 14:43 ` [GIT PULL 3/6] firmware: tegra: " Thierry Reding
2020-11-27 14:43 ` Thierry Reding
2020-11-27 14:43 ` [GIT PULL 4/6] ARM: tegra: Device tree changes " Thierry Reding
2020-11-27 14:43 ` Thierry Reding
2020-11-27 14:43 ` [GIT PULL 5/6] arm64: " Thierry Reding
2020-11-27 14:43 ` Thierry Reding
2020-11-27 19:44 ` Arnd Bergmann [this message]
2020-11-27 19:44 ` Arnd Bergmann
2020-11-27 14:43 ` [GIT PULL 6/6] arm64: tegra: Default configuration " Thierry Reding
2020-11-27 14:43 ` Thierry Reding
2020-11-27 17:10 ` [GIT PULL 1/6] dt-bindings: Changes " patchwork-bot+linux-soc
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='CAK8P3a2vcd0QgfwjTTPM1gk=tTqD+n-4ww-vhJQ3M0z_AZMyDQ@mail.gmail.com' \
--to=arnd@kernel.org \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=soc@kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).