From: Markus Elfring <Markus.Elfring@web.de>
To: Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
Anand Moon <linux.amoon@gmail.com>,
kernel-janitors@vger.kernel.org
Cc: cocci@inria.fr, LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, linux-omap@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Siddharth Vadapalli" <s-vadapalli@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Subject: Re: [cocci] [1/3] PCI: j721e: Propagate dev_err_probe return value
Date: Sun, 19 Oct 2025 19:45:50 +0200 [thread overview]
Message-ID: <53826884-2772-4453-965e-037bf3c4b2ab@web.de> (raw)
In-Reply-To: <26975dab-9631-4661-aaf4-afa213104a13@wanadoo.fr>
…
> Using:
> ret = dev_err_probe(dev, cdns_pcie_init_phy(dev, cdns_pcie), "Failed to
> init phy\n");
>
> 1) is hard to read and understand.
…
I would like to inform you that it can be determined with the help of another
small SmPL script that variations of such assignment expressions are used in
108 source files of the software “Linux next-20251017”.
How will development imaginations evolve further then?
Regards,
Markus
next prev parent reply other threads:[~2025-10-19 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26975dab-9631-4661-aaf4-afa213104a13@wanadoo.fr>
2025-10-19 17:13 ` [cocci] [1/3] PCI: j721e: Propagate dev_err_probe return value Markus Elfring
2025-10-19 17:45 ` Markus Elfring [this message]
[not found] <20251014113234.44418-2-linux.amoon@gmail.com>
[not found] ` <a2cefc72-de44-4a23-92d2-44b58c8c13fe@web.de>
[not found] ` <CANAwSgTtaAtCxtF+DGS-Ay4O3_9JMwk-fJ27yoijhWWbF2URrg@mail.gmail.com>
2025-10-18 11:40 ` Markus Elfring
2025-10-19 16:25 ` Markus Elfring
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=53826884-2772-4453-965e-037bf3c4b2ab@web.de \
--to=markus.elfring@web.de \
--cc=bhelgaas@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).