From: Igor Paunovic <royalnet026@gmail.com>
To: Tomeu Vizoso <tomeu@tomeuvizoso.net>
Cc: Igor Paunovic <royalnet026@gmail.com>,
Oded Gabbay <ogabbay@kernel.org>,
Jiaxing Hu <gahing@gahingwoo.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Sidong Yang <sidong.yang@furiosa.ai>,
Diederik de Haas <diederik@cknow-tech.com>,
Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] accel/rocket: request the core clocks by name
Date: Tue, 11 Aug 2026 23:28:14 +0200 [thread overview]
Message-ID: <20260811212818.10487-1-royalnet026@gmail.com> (raw)
In-Reply-To: <20260729130743.128876-1-royalnet026@gmail.com>
Hi Tomeu,
A gentle ping on this one. It has been on the list since 29 July and has
picked up review and test coverage in the meantime:
Reviewed-by: Jiaxing Hu <gahing@gahingwoo.com>
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Tested-by: Sidong Yang <sidong.yang@furiosa.ai>
Tested-by: Diederik de Haas <diederik@cknow-tech.com> # NanoPC-T6 LTS, NanoPC-T6 Plus
so it now carries two reviews and two independent test reports, covering
the two NanoPC-T6 variants besides my own board.
The reason I am pinging rather than simply waiting: Jiaxing's RK3576
enablement series is based on this patch as of v6,
https://lore.kernel.org/linux-rockchip/20260806063413.350184-1-gahing@gahingwoo.com/
and he has a v7 in preparation. Up to v5 that series carried a duplicate
of the same hunk, which would have conflicted whichever of the two landed
first. Basing on this patch is the right fix, but it does mean his series
is now waiting behind it.
Nothing has changed in the patch itself since v2 and there is no open
comment on it, so it should apply as is. Happy to resend it with the tags
collected if that is easier for you.
Thanks,
Igor
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Igor Paunovic <royalnet026@gmail.com>
To: Tomeu Vizoso <tomeu@tomeuvizoso.net>
Cc: Igor Paunovic <royalnet026@gmail.com>,
Oded Gabbay <ogabbay@kernel.org>,
Jiaxing Hu <gahing@gahingwoo.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Sidong Yang <sidong.yang@furiosa.ai>,
Diederik de Haas <diederik@cknow-tech.com>,
Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] accel/rocket: request the core clocks by name
Date: Tue, 11 Aug 2026 23:28:14 +0200 [thread overview]
Message-ID: <20260811212818.10487-1-royalnet026@gmail.com> (raw)
In-Reply-To: <20260729130743.128876-1-royalnet026@gmail.com>
Hi Tomeu,
A gentle ping on this one. It has been on the list since 29 July and has
picked up review and test coverage in the meantime:
Reviewed-by: Jiaxing Hu <gahing@gahingwoo.com>
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Tested-by: Sidong Yang <sidong.yang@furiosa.ai>
Tested-by: Diederik de Haas <diederik@cknow-tech.com> # NanoPC-T6 LTS, NanoPC-T6 Plus
so it now carries two reviews and two independent test reports, covering
the two NanoPC-T6 variants besides my own board.
The reason I am pinging rather than simply waiting: Jiaxing's RK3576
enablement series is based on this patch as of v6,
https://lore.kernel.org/linux-rockchip/20260806063413.350184-1-gahing@gahingwoo.com/
and he has a v7 in preparation. Up to v5 that series carried a duplicate
of the same hunk, which would have conflicted whichever of the two landed
first. Basing on this patch is the right fix, but it does mean his series
is now waiting behind it.
Nothing has changed in the patch itself since v2 and there is no open
comment on it, so it should apply as is. Happy to resend it with the tags
collected if that is easier for you.
Thanks,
Igor
next prev parent reply other threads:[~2026-08-11 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 13:07 [PATCH v2] accel/rocket: request the core clocks by name Igor Paunovic
2026-07-29 13:07 ` Igor Paunovic
2026-07-29 13:22 ` sashiko-bot
2026-08-02 13:13 ` Sidong Yang
2026-08-02 13:13 ` Sidong Yang
2026-08-05 18:43 ` Diederik de Haas
2026-08-05 18:43 ` Diederik de Haas
2026-08-05 21:15 ` Sebastian Reichel
2026-08-05 21:15 ` Sebastian Reichel
2026-08-11 21:28 ` Igor Paunovic [this message]
2026-08-11 21:28 ` Igor Paunovic
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=20260811212818.10487-1-royalnet026@gmail.com \
--to=royalnet026@gmail.com \
--cc=diederik@cknow-tech.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gahing@gahingwoo.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ogabbay@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=sidong.yang@furiosa.ai \
--cc=tomeu@tomeuvizoso.net \
/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.