From: Markus Elfring <Markus.Elfring@web.de>
To: Andre Przywara <andre.przywara@arm.com>,
Ovidiu Panait <ovidiu.panait.oss@gmail.com>,
linux-sunxi@lists.linux.dev, linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Chen-Yu Tsai <wens@csie.org>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
LKML <linux-kernel@vger.kernel.org>,
Julia Lawall <julia.lawall@inria.fr>
Subject: Re: crypto: sun8i-ce-hash - Refine exception handling in sun8i_ce_hash_run()
Date: Wed, 9 Apr 2025 14:46:28 +0200 [thread overview]
Message-ID: <e10ecbe1-d8c3-444d-92cb-647a1c54675f@web.de> (raw)
In-Reply-To: <20250409133610.59d42bec@donnerap.manchester.arm.com>
>> Two if branches contained duplicate source code.
>> Thus avoid the specification of repeated error code assignments by using
>> additional labels instead.
…
> Now there is one rather opaque label it goes to, so a reader doesn't see
> the error code immediately. And it really just saves one line per case
> here. …
I imagine that such a code refinement can occasionally matter.
Regards,
Markus
next prev parent reply other threads:[~2025-04-09 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 11:43 [PATCH] crypto: sun8i-ce-hash - Refine exception handling in sun8i_ce_hash_run() Markus Elfring
2025-04-09 12:36 ` Andre Przywara
2025-04-09 12:46 ` Markus Elfring [this message]
2025-04-13 7:45 ` Julian Calaby
2025-04-13 8:20 ` Markus Elfring
2025-04-10 6:42 ` [PATCH] " Jernej Škrabec
2025-04-10 9:51 ` 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=e10ecbe1-d8c3-444d-92cb-647a1c54675f@web.de \
--to=markus.elfring@web.de \
--cc=andre.przywara@arm.com \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jernej.skrabec@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=ovidiu.panait.oss@gmail.com \
--cc=samuel@sholland.org \
--cc=wens@csie.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