public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
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-st12, 4.19-cip128
Date: Wed, 28 Jan 2026 14:54:24 +0100	[thread overview]
Message-ID: <aXoVEA630cFSQcO6@duo.ucw.cz> (raw)
In-Reply-To: <604968144.210835.1769572263316@webmail.strato.de>

[-- Attachment #1: Type: text/plain, Size: 1417 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
>

Thank you, patches look okay to me.

Best regards,
								Pavel

a > 121401e5518ea NFSv4: ensure the open stateid seqid doesn't go backwards
a > bac7d26012926 libceph: make calc_target() set t->paused, not just clear it
a > 2c6059deee2ea crypto: af_alg - zero initialize memory allocated via sock_kmalloc
a > 829f2fc2a8274 jbd2: fix the inconsistency between checksum and data in memory for journal sb
a > 0bbbb40b6c0bd f2fs: fix to detect recoverable inode during dryrun of find_fsync_dnodes()
a > dd8bfd7aed8c6 iommu/omap: fix device leaks on probe_device()
a > fd2c1fac2d53a crypto: seqiv - Do not use req->iv after crypto_aead_encrypt
a > d8e936ec8cc01 f2fs: fix return value of f2fs_recover_fsync_data()
a just a preparation > f32fa18502fed ext4: remove unused return value of __mb_check_buddy
a > 7f128710dc0ad clk: renesas: r9a06g032: Fix memory leak in error path
a > 6bfdb8fc2cea5 nbd: defer config put in recv_work
a just a robustness against fs corruption > d81df85afdfef jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted
a > 2a606c6fd4baa NFS: Label the dentry with a verifier in nfs_rmdir() and nfs_unlink()
> 

-- 
In cooperation with Nabla.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2026-01-28 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28  3:51 Request for review for 4.19-st12, 4.19-cip128 Ulrich Hecht
2026-01-28 13:54 ` Pavel Machek [this message]
2026-01-29  6:18 ` 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=aXoVEA630cFSQcO6@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