From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>,
kbuild-all@lists.01.org, lkp@intel.com,
linux-arm-kernel@lists.infradead.org,
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-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: spi-xilinx: fix for_each_child.cocci warnings
Date: Mon, 27 Jun 2022 13:23:09 +0100 [thread overview]
Message-ID: <YrmhLZxSITsSgPcD@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2206261016410.2194@hadrien>
[-- Attachment #1.1: Type: text/plain, Size: 435 bytes --]
On Sun, Jun 26, 2022 at 10:18:46AM -0400, Julia Lawall wrote:
> From: kernel test robot <lkp@intel.com>
>
> for_each_available_child_of_node should have of_node_put() before return around line 697.
> for_each_available_child_of_node should have of_node_put() before break around line 703.
>
> Generated by: scripts/coccinelle/iterators/for_each_child.cocci
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
next prev parent reply other threads:[~2022-06-27 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 14:18 [PATCH] spi: spi-xilinx: fix for_each_child.cocci warnings Julia Lawall
2022-06-27 12:23 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-08 20:51 Julia Lawall
2022-02-09 10:33 ` Ricardo Ribalda Delgado
2022-02-09 13:12 ` Mark Brown
2022-02-09 13:52 ` Ricardo Ribalda Delgado
2022-02-09 13:25 ` Mark Brown
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=YrmhLZxSITsSgPcD@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=lkp@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox