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>,
"pavel@denx.de" <pavel@denx.de>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: Request for reviews for 4.4-st60, 4.4-cip95
Date: Sat, 28 Dec 2024 21:08:29 +0100 [thread overview]
Message-ID: <Z3BavbcAezwkMWZ1@duo.ucw.cz> (raw)
In-Reply-To: <295685651.3780611.1735275418169@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Hi!
> Here's the manual backports for the last release based on 4.19. 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 just a "performance" fix > 8d8dec49e86e5 ubi: wl: Put source PEB into correct list if trying locking LEB failed
a not a minimum fix > 0705b897c226f usb: using mutex lock and supporting O_NONBLOCK flag in iowarrior_read()
a > f8fe313711e34 vfio/pci: Properly hide first-in-list PCIe extended capability
a > bab603ffcb9ca Revert "mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K"
>
> Plus the revert for the broken nilfs2 patch:
>
a > 67baec71e0577 Revert "nilfs2: propagate directory read errors from nilfs_find_entry()"
>
Backports look good to me, thank you.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2024-12-28 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 4:56 Request for reviews for 4.4-st60, 4.4-cip95 Ulrich Hecht
2024-12-28 20:08 ` 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=Z3BavbcAezwkMWZ1@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