From: Pavel Machek <pavel@denx.de>
To: Ulrich Hecht <uli@fpond.eu>
Cc: "pavel@denx.de" <pavel@denx.de>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: Request for reviews for 4.4-st40, 4.4-cip75
Date: Sun, 30 Apr 2023 11:54:21 +0200 [thread overview]
Message-ID: <ZE46zUIujMJ+7/dI@duo.ucw.cz> (raw)
In-Reply-To: <1785763423.1934045.1682608850821@webmail.strato.com>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
Hi!
> Here are the manual backports for the upcoming 4.4-st40 and 4.4-cip75 releases that should be reviewed, and that can currently be found in https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-st-rc
>
> Trivial backports:
These seem ok.
a | 3c29c13c3 968b66 o+ | hwmon (it87): Fix voltage scaling for chips with 10.9mV ADCs
a | 36bfbaa29 b871cb .+ | ALSA: hda/conexant: Partial revert of a quirk for Lenovo
a | 1487976d3 c17f8f f | ALSA: hda/sigmatel: add pin overrides for Intel DP45SG motherboard
a | 078465f34 bf8493 .+ | coresight-etm4: Fix for() loop drvdata->nr_addr_cmp range bug
a | bff19445c ef8327 o | nilfs2: initialize unused bytes in segment summary blocks
Can you doublecheck these?
> ** m | e10703fd5 5d8d4a o+ | arm64: KVM: Fix system register enumeration
AFAICT kvm_arm_copy_core_reg_indices() does not have the problem
described in the changelog, so no change is
neccessary. copy_timer_indices() in 4.4 always return 0 or -EFAULT, so
it does not need changing, either.
> ** m | 3d081d862 c86c00 o+ | i40e: fix i40e_setup_misc_vector() error handling
AFAICT this should be going to end_unlock.
> Not completely trivial backports:
They seem ok.
a | 38d976de6 621489 o+ | hvc/xen: prevent concurrent accesses to the shared ring
a | 1629f6f52 90410b o+ | ocfs2: fix data corruption after failed write
> This is a rather convoluted way to insert a missing prerequisite. It had to be backported because the reverted patch was also a manual backport:
Yep, I seen the "fun" in newer kernels. No problems found here.
a | 65cb67402 67d7d8 o | Revert "ext4: fix use-after-free in ext4_xattr_set_entry"
a | 0a8cff7f0 310c09 o | ext4: remove duplicate definition of ext4_xattr_ibody_inline_set()
a | 322d238b7 67d7d8 o | ext4: fix use-after-free in ext4_xattr_set_entry
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 --]
next prev parent reply other threads:[~2023-04-30 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 15:20 Request for reviews for 4.4-st40, 4.4-cip75 Ulrich Hecht
2023-04-30 9:54 ` Pavel Machek [this message]
2023-05-02 8:50 ` [cip-dev] " Ulrich Hecht
2023-05-02 9:41 ` Pavel Machek
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=ZE46zUIujMJ+7/dI@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--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