From: "Heiko Stübner" <heiko@sntech.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Dragan Simic <dsimic@manjaro.org>
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, Kyle Copperfield <kmcopper@danwin1210.me>
Subject: Re: [PATCH] arm64: dts: rockchip: Add cache information to the SoC dtsi for RK3399
Date: Thu, 04 Jan 2024 10:07:12 +0100 [thread overview]
Message-ID: <2157455.yIU609i1g2@diego> (raw)
In-Reply-To: <fc03e6046bba49b6a4b0794412e0bac6@manjaro.org>
Am Donnerstag, 4. Januar 2024, 09:55:35 CET schrieb Dragan Simic:
> On 2024-01-04 09:51, Krzysztof Kozlowski wrote:
> > On 04/01/2024 09:50, Dragan Simic wrote:
> >> Hello,
> >>
> >> Just checking, is there something preventing this patch from becoming
> >> accepted? I'd appreciate if you'd provide some feedback and let me
> >> know
> >> if there's something in the patch that needs adjusting.
> >
> > Merge window? Is it a fix? If not, the cutoff is around rc5-rc7,
> > depending on your SoC maintainer preferences.
>
> Ah, I see, thanks for the clarification. It isn't a bugfix, so I'll
> send the patch again during the next merge window.
no need to resend.
The main thing holding the patch back was xmas ;-) .
But as Krzysztof wrote, the merge-window is upon us, so I'll pick this up
for 6.9 .
Thanks
Heiko
_______________________________________________
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:[~2024-01-04 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 5:00 [PATCH] arm64: dts: rockchip: Add cache information to the SoC dtsi for RK3399 Dragan Simic
2024-01-04 8:50 ` Dragan Simic
2024-01-04 8:51 ` Krzysztof Kozlowski
2024-01-04 8:55 ` Dragan Simic
2024-01-04 9:07 ` Heiko Stübner [this message]
2024-01-04 9:12 ` Dragan Simic
2024-03-03 19:10 ` Dragan Simic
2024-01-25 21:12 ` Heiko Stuebner
2024-01-25 22:27 ` Dragan Simic
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=2157455.yIU609i1g2@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=kmcopper@danwin1210.me \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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