From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>,
Michal Simek <monstr@monstr.eu>,
Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>,
Tejas Prajapati Rameshchandra <tejaspra@xilinx.com>,
Naga Sureshkumar Relli <nagasure@xilinx.com>,
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kbuild-all@lists.01.org
Subject: Re: [PATCH] spi: spi-xilinx: fix for_each_child.cocci warnings
Date: Wed, 9 Feb 2022 13:25:32 +0000 [thread overview]
Message-ID: <YgPAzIlkrnbn8Vy6@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2202082148490.52266@hadrien>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
On Tue, Feb 08, 2022 at 09:51:30PM +0100, Julia Lawall wrote:
> From: kernel test robot <lkp@intel.com>
>
> After for_each_available_child_of_node, of_node_put is needed before break
> and return.
This doesn't apply against current code, please check and resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>,
Michal Simek <monstr@monstr.eu>,
Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>,
Tejas Prajapati Rameshchandra <tejaspra@xilinx.com>,
Naga Sureshkumar Relli <nagasure@xilinx.com>,
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kbuild-all@lists.01.org
Subject: Re: [PATCH] spi: spi-xilinx: fix for_each_child.cocci warnings
Date: Wed, 9 Feb 2022 13:25:32 +0000 [thread overview]
Message-ID: <YgPAzIlkrnbn8Vy6@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2202082148490.52266@hadrien>
[-- Attachment #1.1: Type: text/plain, Size: 272 bytes --]
On Tue, Feb 08, 2022 at 09:51:30PM +0100, Julia Lawall wrote:
> From: kernel test robot <lkp@intel.com>
>
> After for_each_available_child_of_node, of_node_put is needed before break
> and return.
This doesn't apply against current code, please check and resend.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] spi: spi-xilinx: fix for_each_child.cocci warnings
Date: Wed, 09 Feb 2022 13:25:32 +0000 [thread overview]
Message-ID: <YgPAzIlkrnbn8Vy6@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2202082148490.52266@hadrien>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
On Tue, Feb 08, 2022 at 09:51:30PM +0100, Julia Lawall wrote:
> From: kernel test robot <lkp@intel.com>
>
> After for_each_available_child_of_node, of_node_put is needed before break
> and return.
This doesn't apply against current code, please check and resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-09 13:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 20:51 [PATCH] spi: spi-xilinx: fix for_each_child.cocci warnings Julia Lawall
2022-02-08 20:51 ` Julia Lawall
2022-02-08 20:51 ` Julia Lawall
2022-02-09 10:33 ` Ricardo Ribalda Delgado
2022-02-09 10:33 ` Ricardo Ribalda Delgado
2022-02-09 10:33 ` Ricardo Ribalda Delgado
2022-02-09 13:12 ` Mark Brown
2022-02-09 13:12 ` Mark Brown
2022-02-09 13:12 ` Mark Brown
2022-02-09 13:52 ` Ricardo Ribalda Delgado
2022-02-09 13:52 ` Ricardo Ribalda Delgado
2022-02-09 13:52 ` Ricardo Ribalda Delgado
2022-02-09 13:25 ` Mark Brown [this message]
2022-02-09 13:25 ` Mark Brown
2022-02-09 13:25 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2022-06-26 14:18 Julia Lawall
2022-06-26 14:18 ` Julia Lawall
2022-06-26 14:18 ` Julia Lawall
2022-06-27 12:23 ` Mark Brown
2022-06-27 12:23 ` Mark Brown
2022-06-27 12:23 ` Mark Brown
2022-06-20 17:25 [xilinx-xlnx:xlnx_rebase_v5.15_LTS 861/1181] drivers/spi/spi-xilinx.c:692:1-33: WARNING: Function "for_each_available_child_of_node" should have of_node_put() before return around line 697 kernel test robot
2022-06-20 17:19 ` [PATCH] spi: spi-xilinx: fix for_each_child.cocci warnings kernel test robot
2022-02-08 11:28 [xilinx-xlnx:xlnx_rebase_v5.15 861/872] drivers/spi/spi-xilinx.c:692:1-33: WARNING: Function "for_each_available_child_of_node" should have of_node_put() before return around line 697 kernel test robot
2022-02-08 11:23 ` [PATCH] spi: spi-xilinx: fix for_each_child.cocci warnings kernel test robot
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=YgPAzIlkrnbn8Vy6@sirena.org.uk \
--to=broonie@kernel.org \
--cc=amit.kumar-mahapatra@xilinx.com \
--cc=julia.lawall@inria.fr \
--cc=kbuild-all@lists.01.org \
--cc=lakshmi.sai.krishna.potthuri@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=nagasure@xilinx.com \
--cc=ricardo.ribalda@gmail.com \
--cc=shubhrajyoti.datta@xilinx.com \
--cc=tejaspra@xilinx.com \
/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.