From: Ulrich Hecht <uli@fpond.eu>
To: "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: Request for review for 4.19-st13, 4.19-cip129
Date: Fri, 20 Feb 2026 07:38:46 +0100 (CET) [thread overview]
Message-ID: <1504945381.404757.1771569526446@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
797ce10e2a2f1 macvlan: fix possible UAF in macvlan_forward_source()
85f1f9ce40bf7 HID: uclogic: Correct devm device reference for hidinput input_dev name
0c110bc67bd3d xfs: set max_agbno to allow sparse alloc of last full inode chunk
6a8957a06bc31 l2tp: avoid one data-race in l2tp_tunnel_del_work()
Thanks for having a look!
CU
Uli
next reply other threads:[~2026-02-20 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 6:38 Ulrich Hecht [this message]
2026-02-20 22:39 ` Request for review for 4.19-st13, 4.19-cip129 Pavel Machek
2026-02-21 5:21 ` [cip-dev] " Nobuhiro Iwamatsu (Toshiba)
2026-02-23 4:33 ` 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=1504945381.404757.1771569526446@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