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-st15, 4.19-cip131
Date: Fri, 10 Apr 2026 18:37:55 +0200 [thread overview]
Message-ID: <adknY4VCZ6n0VZCJ@duo.ucw.cz> (raw)
In-Reply-To: <1933779544.248038.1775719721901@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
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
>
a > 630e7903d2418 nfsd: fix return error code for nfsd_map_name_to_[ug]id
a just a robustness against bad hw > 96e0a5c848e8c net: usb: pegasus: enable basic endpoint checking
a > 963b4ef89d7d6 Bluetooth: L2CAP: Fix not checking l2cap_chan security level
a just a preparation, may break compatibility > a973f99e737ba Bluetooth: Enforce key size of 16 bytes on FIPS level
a > bcdd464658030 xfrm6: fix uninitialized saddr in xfrm6_get_saddr()
a just an API fix > 8906907dd0fae netfilter: nf_conntrack: Add allow_clash to generic protocol handler
a > 13c736b3eb26c ext4: don't cache extent during splitting extent
a > cb6f09dc9ae18 apparmor: fix rlimit for posix cpu timers
>
Patches look good to me, thank you!
Best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2026-04-10 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 7:28 Request for review for 4.19-st15, 4.19-cip131 Ulrich Hecht
2026-04-10 16:37 ` 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=adknY4VCZ6n0VZCJ@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