From: Pavel Machek <pavel@denx.de>
To: Ulrich Hecht <uli@fpond.eu>, kazuhiro3.hayashi@toshiba.co.jp
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-st62, 4.4-cip97
Date: Mon, 17 Mar 2025 22:21:41 +0100 [thread overview]
Message-ID: <Z9iSZXvdZiMmPX3e@duo.ucw.cz> (raw)
In-Reply-To: <1265902513.5463957.1741955689526@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
Hi1
> Here's two manual backports for the upcoming 4.4 release. They can be found in the tree at https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-st-rc
>
> ed0c3fd887468 scsi: iscsi: Fix redundant response for
> ISCSI_UEVENT_GET_HOST_STATS request
I'm not sure this causes real problems, but at least it is simple.
> 30e94a5d266d9 irqchip/gic-v3: Handle CPU_PM_ENTER_FAILED correctly
This looks ok to me.
Could we get
[PATCH 4.4 4.9 v1 1/2] init: Introduce system_scheduling flag for allocate_slab()
[PATCH 4.4 4.9 v1 2/2] mm: slub: allocate_slab() enables IRQ right after scheduler starts
Merged into 4.4-st, too? They are simple enough and fix real problem
for Toshiba.
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:[~2025-03-17 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 12:34 Request for reviews for 4.4-st62, 4.4-cip97 Ulrich Hecht
2025-03-17 21:21 ` Pavel Machek [this message]
2025-03-18 7:59 ` [cip-dev] " Ulrich Hecht
2025-03-25 13:46 ` kazuhiro3.hayashi
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=Z9iSZXvdZiMmPX3e@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--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