From: Ulrich Hecht <uli@fpond.eu>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@denx.de" <pavel@denx.de>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Request for review for 4.19-st11, 4.19-cip127
Date: Mon, 22 Dec 2025 07:08:03 +0100 (CET) [thread overview]
Message-ID: <512263003.35605.1766383683487@webmail.strato.de> (raw)
Hi!
Here are the manual backports for the upcoming 4.19 kernel release. 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
0b4f892d4caa usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer
d5e8379424542 scsi: pm80xx: Set phy->enable_completion only when we
82c4ffb49e987 drm/amd/display: Check NULL before accessing
772b21d2f0317 wifi: ath10k: Fix connection after GTK rekeying
7da6f50f7d7a5 pinctrl: single: fix bias pull up/down handling in pin_config_set
80bf4633c7043 libceph: fix potential use-after-free in have_mon_and_osd_map()
495e4a086b69a nvme-fc: use lock accessing port_state and rport state
d6c1721463a61 net: netpoll: fix incorrect refcount handling causing incorrect cleanup
df6e18b2a9179 net: ethernet: ti: netcp: Standardize knav_dma_open_channel to return NULL on error
aa71fdcea176e tipc: Fix use-after-free in tipc_mon_reinit_self().
92396463b534a sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto
4051e60b1c5fc Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF
ef3aaa87ec116 net: ravb: Enforce descriptor type ordering
dd2973f30a943 wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode
22a3a715eb41f net/sched: sch_qfq: Fix null-deref in agg_dequeue
Thanks for having a look!
CU
Uli
next reply other threads:[~2025-12-22 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 6:08 Ulrich Hecht [this message]
2026-01-05 21:55 ` Request for review for 4.19-st11, 4.19-cip127 Pavel Machek
2026-01-08 2:58 ` [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=512263003.35605.1766383683487@webmail.strato.de \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@denx.de \
/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