From: Markus Elfring <Markus.Elfring@web.de>
To: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>, Jiri Pirko <jiri@resnulli.us>,
Madalin Bucur <madalin.bucur@nxp.com>,
Paolo Abeni <pabeni@redhat.com>,
Sean Anderson <sean.anderson@seco.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: net: fman: Use common error handling code in dtsec_init()
Date: Wed, 28 Feb 2024 09:43:35 +0100 [thread overview]
Message-ID: <99ea976a-2a37-4656-b370-53daaff54c49@web.de> (raw)
In-Reply-To: <20240227184657.76ec4e82@kernel.org>
>> Adjust jump targets so that a bit of exception handling can be better
>> reused at the end of this function implementation.
>
> Okay, but..
>
>> .../net/ethernet/freescale/fman/fman_dtsec.c | 19 +++++++++++--------
>> 1 file changed, 11 insertions(+), 8 deletions(-)
>
> ..you've added more lines than you've removed so what's the point.
* Can the change acceptance grow any more for attempts to improve error handling
another bit?
* Would you like to fiddle with scope-based resource management?
https://elixir.bootlin.com/linux/v6.8-rc6/source/include/linux/cleanup.h#L8
See also:
Article by Jonathan Corbet from 2023-06-15
https://lwn.net/Articles/934679/
> --
> pw-bot: reject
Can such an reaction be reconsidered once more?
Regards,
Markus
prev parent reply other threads:[~2024-02-28 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 13:14 [PATCH] net: fman: Use common error handling code in dtsec_init() Markus Elfring
2024-02-27 13:54 ` Madalin Bucur (OSS)
2024-02-27 15:42 ` Jiri Pirko
2024-02-28 2:46 ` Jakub Kicinski
2024-02-28 7:51 ` Jiri Pirko
2024-02-28 14:59 ` Dan Carpenter
2024-02-28 8:43 ` Markus Elfring [this message]
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=99ea976a-2a37-4656-b370-53daaff54c49@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.anderson@seco.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 NNTP newsgroup(s).