From: Jonas Rebmann <jre@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
"open list:BAREBOX" <barebox@lists.infradead.org>
Cc: Lukas Wunner <lukas@wunner.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
Jonas Rebmann <jre@pengutronix.de>,
Stefan Berger <stefanb@linux.ibm.com>,
Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Thorsten Blum <thorsten.blum@linux.dev>
Subject: [PATCH 0/4] crypto: Port ecc.c fixes from kernel
Date: Mon, 18 May 2026 09:56:12 +0200 [thread overview]
Message-ID: <20260518-barebox-port-ecc-v1-0-25509bd37030@pengutronix.de> (raw)
We've been working on processes for porting fixes from copied code in
winter and introduced Origin-URL references [1] during those
discussions.
Now thanks to Lukas we're reminded to put this to practice.
This series is a proposal on future standard practice of porting such
patches: Update the Origin-URL in every ported patch, mention the origin
project in the "cherry picked from" line. Handle like a backport for all
other regards.
Note that the most recent ported patch is linux commit c66e0a273f22
("crypto: ecc - Streamline alloc_point and remove
{alloc,free}_digits_space") but Origin-URL is pointing at commit
d6ea871d73ab ("crypto: ecc - Use crypto_stdrng_get_bytes()"), which I
intentionally skipped when porting as not applicable to barebox (we have
a different random bytes API). This is so that the file is now
recognizable as up to date until further updates on linux master.
To establish these processes, we should soon underscore them with some
tooling like Ahmad did in [1].
[1] https://lore.kernel.org/barebox/20251218151807.691382-1-a.fatoum@pengutronix.de/
Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
---
Jonas Rebmann (1):
crypto: ecc: Add Origin-URL to document kernel revision
Lukas Wunner (1):
crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP()
Stefan Berger (1):
crypto: ecc - Fix off-by-one missing to clear most significant digit
Thorsten Blum (1):
crypto: ecc - Streamline alloc_point and remove {alloc,free}_digits_space
crypto/ecc.c | 32 ++++++++++++--------------------
include/linux/math.h | 12 ++++++++++++
2 files changed, 24 insertions(+), 20 deletions(-)
---
base-commit: c7bdd78be7cc9449a49a429a342c83f8085b1475
change-id: 20260515-barebox-port-ecc-1d6e25c9608c
Best regards,
--
Jonas Rebmann <jre@pengutronix.de>
next reply other threads:[~2026-05-18 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 7:56 Jonas Rebmann [this message]
2026-05-18 7:56 ` [PATCH 1/4] crypto: ecc: Add Origin-URL to document kernel revision Jonas Rebmann
2026-05-18 7:56 ` [PATCH 2/4] crypto: ecc - Fix off-by-one missing to clear most significant digit Jonas Rebmann
2026-05-18 7:56 ` [PATCH 3/4] crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() Jonas Rebmann
2026-05-18 7:56 ` [PATCH 4/4] crypto: ecc - Streamline alloc_point and remove {alloc,free}_digits_space Jonas Rebmann
2026-05-18 13:25 ` [PATCH 0/4] crypto: Port ecc.c fixes from kernel Sascha Hauer
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=20260518-barebox-port-ecc-v1-0-25509bd37030@pengutronix.de \
--to=jre@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=lukas@wunner.de \
--cc=s.hauer@pengutronix.de \
--cc=stefanb@linux.ibm.com \
--cc=thorsten.blum@linux.dev \
--cc=venkat88@linux.vnet.ibm.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