From: Pavel Machek <pavel@denx.de>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: Request for review for 4.19-st8, 4.19-cip124
Date: Thu, 18 Sep 2025 10:04:00 +0200 [thread overview]
Message-ID: <aMu88B3vQn1iC0Lu@duo.ucw.cz> (raw)
In-Reply-To: <1522250355.247103.1758035031215@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1500 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
> (At least that's what I assume; I'm no longer able to get past the bot protection...)
I have seen it randomly fail on me, too. Could LF tone it down?
Patches look ok to me, ddc44ffdaa7d8 should probably return
-EFSCORRUPTED but I doubt anyone cares.
Best regards,
Pavel
a just a robustness against fs corruption > c50175dd232f1 f2fs: fix to do sanity check on ino and xnid
a > c5da7386ca038 squashfs: fix memory leak in squashfs_fill_super
a critical section could be shorter > 8004a014004f3 pNFS: Handle RPC size limit for layoutcommits
a > 73d1fa319709c wifi: iwlwifi: fw: Fix possible memory leak in iwl_fw_dbg_collect
a just a printk tweak > a2cab05b5667d usb: core: usb_submit_urb: downgrade type check
a just a robustness against fs corruption, -EFSCORRUPTED? > ddc44ffdaa7d8 udf: Verify partition map count
a just a robustness against fs corruption > 68def4bf2c714 f2fs: fix to avoid panic in f2fs_evict_inode
a > a2f0f298a3bc6 usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm
a just a robustness against fs corruption > 0f86291316a33 f2fs: fix to avoid out-of-boundary access in dnode page
>
--
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-09-18 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 15:03 Request for review for 4.19-st8, 4.19-cip124 Ulrich Hecht
2025-09-18 8:04 ` Pavel Machek [this message]
2025-09-18 12:28 ` 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=aMu88B3vQn1iC0Lu@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--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