From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Rob Herring <robh@kernel.org>, Barry Song <baohua@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
kernel-janitors@vger.kernel.org,
Patrice Chotard <patrice.chotard@st.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: Re: pinctrl: sirf: Use common error handling code in sirfsoc_dt_node_to_map()
Date: Mon, 30 Oct 2017 20:32:15 +0100 [thread overview]
Message-ID: <72b04f56-be81-5a7d-3a43-abac41dd05ba@users.sourceforge.net> (raw)
In-Reply-To: <CAMuHMdXSVXZNW7a-xf_zyCW-j_KVQbRBdrt8q-SNjGChuDU-bw@mail.gmail.com>
>> Add a jump target so that a bit of exception handling can be better reused
>> at the end of this function.
>>
>> This issue was detected by using the Coccinelle software.
>
> Does Coccinelle have a threshold for how much cleanup can be shared?
Are you looking for a limitation of such source code search patterns?
Regards,
Markus
next prev parent reply other threads:[~2017-10-30 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 18:36 [PATCH] pinctrl: sirf: Use common error handling code in sirfsoc_dt_node_to_map() SF Markus Elfring
2017-10-30 19:15 ` Geert Uytterhoeven
2017-10-30 19:32 ` SF Markus Elfring [this message]
2017-10-30 19:34 ` Geert Uytterhoeven
2017-10-30 19:41 ` SF Markus Elfring
2017-11-01 10:33 ` [PATCH] " Dan Carpenter
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=72b04f56-be81-5a7d-3a43-abac41dd05ba@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=Julia.Lawall@lip6.fr \
--cc=baohua@kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=patrice.chotard@st.com \
--cc=robh@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).