From: Ulrich Hecht <uli@fpond.eu>
To: pavel@nabladev.com
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Re: [cip-dev] Request for review for 4.19-st20, 4.19-cip136
Date: Thu, 10 Sep 2026 10:09:42 +0200 (CEST) [thread overview]
Message-ID: <1507273529.285330.1789027782094@webmail.strato.de> (raw)
In-Reply-To: <ap6aPwQoEtRazAe9@duo.ucw.cz>
> On 09/07/2026 1:04 PM CEST Pavel Machek via lists.cip-project.org <pavel=nabladev.com@lists.cip-project.org> wrote:
> More reviews here.
Thank you!
> ! this is now completely different from mainline, and pretty non
> trivial; I don't know how to review this one > 0ee0719ebd182 crypto: af_alg - Remove zero-copy support from skcipher and aead
It's almost identical to the 5.10 patch, with the only change being that ITER_SOURCE is replaced by "WRITE | ITER_BVEC" because 4.19 predates "iov_iter: Separate type from direction and use accessor functions".
This entire kernel tree is based on the assumption that 5.10 patches are (at least conceptually) correct for 5.10, and with the code being completely identical in 4.19 I'm inclined to believe that in this case the 5.10 patch is correct for 4.19 as well.
CU
Uli
next prev parent reply other threads:[~2026-09-10 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 18:32 Request for review for 4.19-st20, 4.19-cip136 Ulrich Hecht
2026-09-03 9:00 ` Pavel Machek
2026-09-03 9:18 ` Ulrich Hecht
2026-09-03 11:59 ` Pavel Machek
2026-09-10 8:09 ` [cip-dev] " Ulrich Hecht
2026-09-07 11:04 ` Pavel Machek
2026-09-10 8:09 ` Ulrich Hecht [this message]
2026-09-09 19:23 ` Pavel Machek
2026-09-10 19:32 ` Pavel Machek
2026-09-11 10:15 ` [cip-dev] " Ulrich Hecht
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=1507273529.285330.1789027782094@webmail.strato.de \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.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