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-st72, 4.4-cip107
Date: Tue, 3 Feb 2026 12:45:59 +0100 [thread overview]
Message-ID: <aYHf9zpDUEwBm1fS@duo.ucw.cz> (raw)
In-Reply-To: <1873813255.141036.1770094885595@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 919 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
>
a > 9fdef2a6b53b3 jbd2: fix the inconsistency between checksum and data in memory for journal sb
a > 7d0ef9b50d5d3 f2fs: fix return value of f2fs_recover_fsync_data()
a > bb471f70de075 ip6_gre: make ip6gre_header() robust
a just a WARN addition > 6eaf989ce1c09 KVM: x86: WARN if hrtimer callback for periodic APIC timer fires with period=0
a > 1a0a3e2a74b85 f2fs: invalidate dentry cache on failed whiteout creation
a > cdfaae22c3796 usb: renesas_usbhs: Fix a resource leak in usbhs_pipe_malloc()
>
Patches look good to me, thank you.
Reviewed-by: Pavel Machek <pavel@nabladev.com>
Best regards,
Pavel
--
In cooperation with Nabla.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2026-02-03 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 5:01 Request for review for 4.4-st72, 4.4-cip107 Ulrich Hecht
2026-02-03 11:45 ` 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=aYHf9zpDUEwBm1fS@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