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.4-st64, 4.4-cip99
Date: Wed, 14 May 2025 12:02:25 +0200 [thread overview]
Message-ID: <aCRqMeCYmmC2pFVm@duo.ucw.cz> (raw)
In-Reply-To: <594897735.236352.1747215068214@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Hi!
> Here's the manual backports for the upcoming 4.4 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.4.y-st-rc
>
These are ok:
a GFP_KERNEL failures are mostly theoretical > 21503a13375d5 qlcnic: fix memory leak issues in qlcnic_sriov_common.c
a just a hw bug workaround > 952bc6f3a0ebb HID: ignore non-functional sensor in HP 5MP Camera
Are you sure about this one?
!! > ece0f8e21aa7f net_sched: Prevent creation of classes with TC_H_ROOT
Unlike newer kernels, out: has non-trivial cleanup, so we probably
want to goto there.
> There is also one new patch that I added mostly for my own benefit:
>
> 18a3ce42a20f0 mm/sparsemem: silence "'mem_section' will never be NULL" warning
Looks good. I'd quote commit id in the log ...
This is similar in function to the upstream patch
a431dbbc540532b7465eae4fc8b56a85a9fc7d17 "mm/sparsemem: fix
'mem_section' will never be NULL gcc 12 warning" but avoids adding
extra checks to minimize the potential for regressions.
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-05-14 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 9:31 Request for review for 4.4-st64, 4.4-cip99 Ulrich Hecht
2025-05-14 10:02 ` Pavel Machek [this message]
2025-05-15 12:38 ` [cip-dev] " Ulrich Hecht
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=aCRqMeCYmmC2pFVm@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