From: Nathan Chancellor <nathan@kernel•org>
To: Nicolas Dufresne <nicolas@ndufresne•ca>
Cc: Detlev Casanova <detlev.casanova@collabora•com>,
Ezequiel Garcia <ezequiel@vanguardiasur•com.ar>,
Mauro Carvalho Chehab <mchehab@kernel•org>,
Heiko Stuebner <heiko@sntech•de>, Brian Cain <bcain@kernel•org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail•com>,
Bill Wendling <morbo@google•com>,
Justin Stitt <justinstitt@google•com>,
linux-media@vger•kernel.org, linux-rockchip@lists•infradead.org,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, linux-hexagon@vger•kernel.org,
llvm@lists•linux.dev
Subject: Re: [PATCH] media: rockchip: Disable VIDEO_ROCKCHIP_VDEC when compile testing for Hexagon
Date: Fri, 27 Mar 2026 23:11:02 +0100 [thread overview]
Message-ID: <20260327221102.GA3621310@ax162> (raw)
In-Reply-To: <1a618af9b6c311e8fe5db64ff6fb7c1872c7b2b6.camel@ndufresne.ca>
On Thu, Mar 19, 2026 at 04:08:29PM -0400, Nicolas Dufresne wrote:
> I haven't heard back about the port to plain bitwriter. I guess I have to pick
> this patch, but I really don't want to have to maintain too many of these hacks.
> Anyone else with an opinion on the topic ? Or a better idea how this can be
> workaround differently ?
I ended up retesting this recently after I saw Denis posted a bitwriter
series and it turns out that Arnd's commit 446c6a25a449 ("media: rkvdec:
reduce excessive stack usage in assemble_hw_pps()") is enough to avoid
this issue, so you can disregard this change.
Cheers,
Nathan
prev parent reply other threads:[~2026-03-27 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 20:10 [PATCH] media: rockchip: Disable VIDEO_ROCKCHIP_VDEC when compile testing for Hexagon Nathan Chancellor
2026-02-16 16:17 ` Nicolas Dufresne
2026-03-19 20:08 ` Nicolas Dufresne
2026-03-19 20:24 ` Nathan Chancellor
2026-03-27 22:11 ` Nathan Chancellor [this message]
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=20260327221102.GA3621310@ax162 \
--to=nathan@kernel$(echo .)org \
--cc=bcain@kernel$(echo .)org \
--cc=detlev.casanova@collabora$(echo .)com \
--cc=ezequiel@vanguardiasur$(echo .)com.ar \
--cc=heiko@sntech$(echo .)de \
--cc=justinstitt@google$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-hexagon@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=mchehab@kernel$(echo .)org \
--cc=morbo@google$(echo .)com \
--cc=nick.desaulniers+lkml@gmail$(echo .)com \
--cc=nicolas@ndufresne$(echo .)ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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