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: Mon, 2 Nov 2026 12:36:17 +0100 [thread overview]
Message-ID: <auh1sRkdmg3AWRbt@duo.ucw.cz> (raw)
In-Reply-To: <1931298540.80350.1793132613065@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1578 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
>
These look ok to me:
Reviewed-by: Pavel Machek <pavel@nabladev.com>
a this is not easy to validate > 0f9dd2fd36dc88 ipv4: validate checksum_start before completing checksum
a > 1aef1ed67bf592 netfilter: ip6t_rt: fix zero-address non-strict match out-of-bounds read
a > 1772d2f27fe10f net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry
a > 994be280b21cd2 net/sched: reject IDR error pointers when deleting actions
a > 2548133fd1bde9 drm/nouveau: Fix gem reference leak in validate_init()
a > 893066ca3560ef drm/nouveau: fix double-free in nvif_vmm_dtor
> a91fd56ecf47a4 gpio: zynq: fix runtime PM leak on request error path
So this is common pattern and quite a common mistake. As it only
happens in error paths, we may want to simply ignore this one.
If we wanted this fixed, we should probably introduce
pm_runtime_resume_and_get(). We already have two users of the
non-existing function in the tree, so two compile errors waiting to happen.
drivers/irqchip/irq-gic-pm.c: ret = pm_runtime_resume_and_get(dev);
sound/ac97/bus.c: ret = pm_runtime_resume_and_get(dev);
Best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-11-02 11:36 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 [this message]
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
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=auh1sRkdmg3AWRbt@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