From: Markus Elfring <Markus.Elfring@web.de>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Miaoqian Lin <linmq006@gmail.com>,
linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Hans Verkuil <hverkuil@kernel.org>,
Joe Hattori <joe@pf.is.s.u-tokyo.ac.jp>,
Magnus Damm <magnus.damm@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
Subject: Re: [PATCH] media: renesas: rcar_drif: fix device node reference leak in rcar_drif_bond_enabled
Date: Wed, 3 Sep 2025 18:45:15 +0200 [thread overview]
Message-ID: <b1c54922-ce1e-4259-b66b-f0d3f0a2d7f1@web.de> (raw)
In-Reply-To: <CAMuHMdWBXv+vKqBXOWeFqsy0R8-3__oBFWnm4rUx1kqSq5ZUgQ@mail.gmail.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Are any description details still improvable?
> Note that this is a duplicate of "[PATCH] media: rcar_drif: Fix an OF
> node leak in rcar_drif_bond_enabled()", which was never applied.
>
> [1] https://lore.kernel.org/20250105111050.3859712-1-joe@pf.is.s.u-tokyo.ac.jp
Would it be nicer (in principle) to integrate this patch finally?
Regards,
Markus
next prev parent reply other threads:[~2025-09-03 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 13:37 [PATCH] media: renesas: rcar_drif: fix device node reference leak in rcar_drif_bond_enabled Miaoqian Lin
2025-09-03 15:09 ` Geert Uytterhoeven
2025-09-03 16:45 ` Markus Elfring [this message]
2025-11-03 10:29 ` Hans Verkuil
2025-09-03 17:14 ` Fabrizio Castro
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=b1c54922-ce1e-4259-b66b-f0d3f0a2d7f1@web.de \
--to=markus.elfring@web.de \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=hverkuil@kernel.org \
--cc=joe@pf.is.s.u-tokyo.ac.jp \
--cc=linmq006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mchehab@kernel.org \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).