From: Heiko Stuebner <heiko@sntech.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: arm@kernel.org, soc@kernel.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip dts64 changes for 7.1 #1
Date: Tue, 17 Mar 2026 10:08:48 +0100 [thread overview]
Message-ID: <2031768.PYKUYFuaPT@phil> (raw)
In-Reply-To: <20260317-impetuous-attentive-penguin-43a503@quoll>
Am Dienstag, 17. März 2026, 09:48:30 Mitteleuropäische Normalzeit schrieb Krzysztof Kozlowski:
> On Sat, Mar 14, 2026 at 07:45:34PM +0100, Heiko Stuebner wrote:
> > Hi soc maintainers,
> >
> > please find below Rockchip DT changes for the merge-window for 7.1 .
> >
> > So far only arm64 changes :-)
> >
> >
> > Please pull.
> > Thanks
> > Heiko
> >
> >
> > The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> >
> > Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> >
> > are available in the Git repository at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v7.1-rockchip-dts64-1
>
> Next analysis reports:
>
> Days in linux-next:
> ----------------------------------------
> 1 | + (1)
> 2 |
> 3 |
> 4 | + (1)
>
> Please keep changes in next for at least few releases, in case of
> development pulls. Allow community to actually test your code before you
> send it to upstream maintainer. We are early in the cycle, so there is
> no need to rush changes which were almost not in next.
okay, will adapt to the faster pacing of PRs getting looked at.
In the past I was trying to make Arnd's life easier (not sure if that
helped or not) with the PR available, so that he could get to them when
he had time.
Heiko
next prev parent reply other threads:[~2026-03-17 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 18:45 [GIT PULL] Rockchip dts64 changes for 7.1 #1 Heiko Stuebner
2026-03-17 8:48 ` Krzysztof Kozlowski
2026-03-17 9:08 ` Heiko Stuebner [this message]
2026-03-21 11:05 ` 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=2031768.PYKUYFuaPT@phil \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox