public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	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>,
	Anand Moon <linux.amoon@gmail.com>
Subject: Re: [PATCH] arm64: dts: rockchip: Add cache information to the SoC dtsi for RK3399
Date: Sun, 03 Mar 2024 20:10:25 +0100	[thread overview]
Message-ID: <a9f7d25d3fc89fb5ea1b2c2c72fb2682@manjaro.org> (raw)
In-Reply-To: <7e1d4611079375f92f6ab7d446160200@manjaro.org>

Hello Heiko,

On 2024-01-04 10:12, Dragan Simic wrote:
> On 2024-01-04 10:07, Heiko Stübner wrote:
>> 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:
>>> >> 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 .
> 
> Awesome, thank you! :)  I'll move forward and prepare a few more
> similar patches for other Rockchip SoCs, after I recover from some
> nasty flu I've unfortunately contracted.

It took me a while, but pretty much the same patches for the RK3328 [1]
and the RK356x [2] are now on the mailing list.  Please, have a look.

[1] 
https://lore.kernel.org/linux-rockchip/e61173d87f5f41af80e6f87f8820ce8d06f7c20c.1709491127.git.dsimic@manjaro.org/
[2] 
https://lore.kernel.org/linux-rockchip/2285ee41e165813011220f9469e28697923aa6e0.1709491108.git.dsimic@manjaro.org/

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-03-03 19:10 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
2024-01-04  9:12         ` Dragan Simic
2024-03-03 19:10           ` Dragan Simic [this message]
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=a9f7d25d3fc89fb5ea1b2c2c72fb2682@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --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=linux.amoon@gmail.com \
    --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