From: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-clk@vger.kernel.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
robh@kernel.org, conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v13 2/5] drm/imx: Add support for i.MX94 DCIF
Date: Fri, 20 Nov 2026 15:21:33 +0200 [thread overview]
Message-ID: <awBJBXRvvADJDwEv@vm> (raw)
In-Reply-To: <sashiko-outbox-225210@kernel.org>
On Fri, Nov 20, 2026 at 01:16:15PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential
> issues to consider:
> - [Medium] drm/imx/dcif: unclocked MMIO access after
> pm_runtime_resume_and_get() fails
> - [Medium] drm/imx: dcif: unbalanced clock disable if
> dcif_runtime_resume() fails
I mentioned in my reply to v12 comments why is not worth addressing these two:
https://lore.kernel.org/r/awAgaVs4LLwqVA57@vm
--
Thanks,
Laurentiu
next prev parent reply other threads:[~2026-11-20 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 12:50 [PATCH v13 0/5] Add support for i.MX94 DCIF Laurentiu Palcu
2026-11-20 12:50 ` [PATCH v13 1/5] dt-bindings: display: imx: Add " Laurentiu Palcu
2026-11-20 12:50 ` [PATCH v13 2/5] drm/imx: Add support for " Laurentiu Palcu
2026-11-20 13:16 ` sashiko-bot
2026-11-20 13:21 ` Laurentiu Palcu [this message]
2026-11-20 12:50 ` [PATCH v13 3/5] dt-bindings: clock: nxp,imx95-blk-ctl: Add LDB bridge child node Laurentiu Palcu
2026-11-20 12:50 ` [PATCH v13 3/5] dt-bindings: clock: nxp, imx95-blk-ctl: " Laurentiu Palcu
2026-11-20 12:50 ` [PATCH v13 4/5] arm64: dts: imx94: Add display pipeline nodes Laurentiu Palcu
2026-11-20 12:50 ` [PATCH v13 5/5] arm64: dts: imx943-evk: Add display support using IT6263 Laurentiu Palcu
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=awBJBXRvvADJDwEv@vm \
--to=laurentiu.palcu@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=linux-clk@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.