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.4-st75, 4.4-cip110
Date: Thu, 23 Apr 2026 12:00:14 +0200 [thread overview]
Message-ID: <aentrtAsop2UI7t1@duo.ucw.cz> (raw)
In-Reply-To: <310741778.1030622.1776850439887@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Hi!
> Here are the manual backports for the upcoming 4.4 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.4.y-st-rc
>
Patches look okay to me, thank you!
Best regards,
Pavel
a just a robustness against malicious hw > 7c091280e3bb2 net: usb: pegasus: enable basic endpoint checking
a > e2727eb73284b ceph: supply snapshot context in ceph_zero_partial_object()
a just an API fix> 2574b34a8eb2d xen-netback: reject zero-queue configuration from guest
a quite complex/e > 14894a8decc71 net: atm: fix crash due to unvalidated vcc pointer in sigd_send()
a > de412dd7471d2 PCI/portdrv: Fix potential resource leak
a just a tracing fix > 1837000f16f5e hrtimer: Fix trace oddity
a > 5525cf4093568 md/raid10: fix any_working flag handling in raid10_sync_request
a just a robustness against malicious hw > 554c2968593e9 net: usb: catc: enable basic endpoint checking
>
> Thanks for having a look!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-04-23 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 9:33 Request for review for 4.4-st75, 4.4-cip110 Ulrich Hecht
2026-04-23 10:00 ` Pavel Machek [this message]
2026-04-23 23:11 ` [cip-dev] " nobuhiro.iwamatsu.x90
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=aentrtAsop2UI7t1@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