From: Hugues FRUCHET <hugues.fruchet@st.com>
To: Nicholas Mc Guire <hofrat@osadl.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
Niklas Soderlund <niklas.soderlund+renesas@ragnatech.se>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: stm32-dcmi: simplify of_node_put usage
Date: Mon, 18 Jun 2018 09:36:28 +0000 [thread overview]
Message-ID: <1b951a4b-4583-5cc2-c54a-4de1196e1653@st.com> (raw)
In-Reply-To: <1528824196-19149-1-git-send-email-hofrat@osadl.org>
Hi Nicholas,
Thanks for patch,
On 06/12/2018 07:23 PM, Nicholas Mc Guire wrote:
> This does not fix any bug - this is just a code simplification. As
> np is not used after passing it to v4l2_fwnode_endpoint_parse() its
> refcount can be decremented immediately and at one location.
>
> Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
Acked-by: Hugues Fruchet <hugues.fruchet@st.com>
> ---
>
> Issue found during code reading.
>
> Patch was compile tested with: x86_64_defconfig, MEDIA_SUPPORT=y
> MEDIA_CAMERA_SUPPORT=y, V4L_PLATFORM_DRIVERS=y, OF=y, COMPILE_TEST=y
> CONFIG_VIDEO_STM32_DCMI=y
> (There are a few sparse warnings - but unrelated to the lines changed)
>
> Patch is against 4.17.0 (localversion-next is next-20180608)
>
> drivers/media/platform/stm32/stm32-dcmi.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/media/platform/stm32/stm32-dcmi.c b/drivers/media/platform/stm32/stm32-dcmi.c
> index 2e1933d..0b61042 100644
> --- a/drivers/media/platform/stm32/stm32-dcmi.c
> +++ b/drivers/media/platform/stm32/stm32-dcmi.c
> @@ -1696,23 +1696,20 @@ static int dcmi_probe(struct platform_device *pdev)
> }
>
> ret = v4l2_fwnode_endpoint_parse(of_fwnode_handle(np), &ep);
> + of_node_put(np);
> if (ret) {
> dev_err(&pdev->dev, "Could not parse the endpoint\n");
> - of_node_put(np);
> return -ENODEV;
> }
>
> if (ep.bus_type == V4L2_MBUS_CSI2) {
> dev_err(&pdev->dev, "CSI bus not supported\n");
> - of_node_put(np);
> return -ENODEV;
> }
> dcmi->bus.flags = ep.bus.parallel.flags;
> dcmi->bus.bus_width = ep.bus.parallel.bus_width;
> dcmi->bus.data_shift = ep.bus.parallel.data_shift;
>
> - of_node_put(np);
> -
> irq = platform_get_irq(pdev, 0);
> if (irq <= 0) {
> dev_err(&pdev->dev, "Could not get irq\n");
>
next prev parent reply other threads:[~2018-06-18 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 17:23 Nicholas Mc Guire
2018-06-18 9:36 ` Hugues FRUCHET [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-10 15:23 Nicholas Mc Guire
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=1b951a4b-4583-5cc2-c54a-4de1196e1653@st.com \
--to=hugues.fruchet@st.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=garsilva@embeddedor.com \
--cc=hans.verkuil@cisco.com \
--cc=hofrat@osadl.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=p.zabel@pengutronix.de \
/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
all inboxes | Powered by JetHome®