From: Pavel Machek <pavel@nabladev.com>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@nabladev.com" <pavel@nabladev.com>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Re: Request for review for 4.19-st21, 4.19-cip137
Date: Wed, 11 Nov 2026 22:15:07 +0100 [thread overview]
Message-ID: <avTa2yGNm2t15IMc@duo.ucw.cz> (raw)
In-Reply-To: <1931298540.80350.1793132613065@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
Hi!
> Here are the adapted backports for the upcoming 4.19 kernel release. There's a total of 95; 1 written by me, 2 by Qwen-3.8-27B and 92 by Qwen-3.8-Flash-Next. (The latter are labeled with "Assisted-by: SLTR:qwen-3.8" and "Assisted-by: SLTR:qwen-3.8-flash-next", respectively.)
>
> As always they can be found in https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-st-rc
I was able to review few more commits.
Reviewed-by: Pavel Machek <pavel@nabladev.com> .
Best regards,
Pavel
a mostly theoretical, GFP_KERNEL allocations do not fail > d7b349ebdfdafc ASoC: meson: Keep link pointers valid on realloc failure
a just a config tweak > d38f463c73bccc tty: hvc: restrict HVC_DCC to ARMv6+ and ARM64
a > 1b1bd4efd7d8a1 iommu/amd: Prevent SB IOAPIC from overriding IVRS validation errors
a just a of refcount leak > 05c7c199894226 soc: samsung: exynos-pmu: fix of_node refcount leak in exynos_get_pmu_regmap()
a > 53a94e6cc49ffe mtd: rawnand: validate ONFI extended parameter page sections
a just a robustness > 303a77ac1be15b selinux: reject an unclaimed class value in security_get_classes()
a > 4fae216b4a1760 tcp: fix potential race in tcp_v6_syn_recv_sock()
a not quite trivial, just a interface fix > 393c2ca46a3b27 fsnotify: Fix stale object mask after concurrent mark updates
a > aea3fa3f950c8c net: cap advertised IP tunnel headroom
a > ce12d5b2bdee84 net: openvswitch: fix flow mask use-after-free on flow deletion
a > f139bc5bef5bc9 power: supply: max17040: synchronize work cancellation on suspend
a > 7c74c8f9a71e98 sctp: fix stream->outcnt underflow on duplicate RECONF responses
a just a api change, may break someone's setup > 3a1fe75c4db943 mm/swap: reject swapon() on filesystem-level encrypted files
a just a robustness > 4084800d553361 selinux: switch two allocations to use kzalloc_objs()
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2026-11-11 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 20:23 Request for review for 4.19-st21, 4.19-cip137 Ulrich Hecht
2026-11-02 11:36 ` Pavel Machek
2026-11-03 9:22 ` Ulrich Hecht
2026-11-05 19:07 ` Pavel Machek
2026-11-06 10:03 ` Pavel Machek
2026-11-09 16:49 ` [cip-dev] " Ulrich Hecht
2026-11-10 21:27 ` Pavel Machek
2026-11-12 10:53 ` Ulrich Hecht
2026-11-11 21:15 ` Pavel Machek [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=avTa2yGNm2t15IMc@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=uli@fpond.eu \
/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