public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
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-st61, 4.4-cip96
Date: Wed, 12 Feb 2025 17:58:04 +0100	[thread overview]
Message-ID: <Z6zTHNwhODhmeQId@duo.ucw.cz> (raw)
In-Reply-To: <707882010.596091.1739240064075@webmail.strato.de>

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

Hi!

> Here's the manual backports for the next 4.4 kernel release. 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
> 
> Seems like all manual backports to 4.19 applied cleanly, so there is nothing to re-review.
> 
a 65a3da457f648 phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup()
a fbb00ee18cfb9 batman-adv: Remove uninitialized data in full table TT response
a b317a37e42dbc leds: class: Protect brightness_show() with led_cdev->led_access mutex
a 20e3dfc5e6312 net: inet: do not leave a dangling sk pointer in inet_create()
a 9f3769378767d af_packet: avoid erroring out after sock_init_data() in packet_create()
a dc4d74d36b1bc nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry()

These look good to me.

> e2f28a0cb0a81 netfilter: x_tables: fix LED ID check in led_tg_check()

It is strange to use memchr for this, and memchr second argument is
integer. But if the patch was good enough for mainline, I think we can
live with it.

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 --]

  reply	other threads:[~2025-02-12 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11  2:14 Request for reviews for 4.4-st61, 4.4-cip96 Ulrich Hecht
2025-02-12 16:58 ` Pavel Machek [this message]
2025-02-12 22:21 ` nobuhiro1.iwamatsu

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=Z6zTHNwhODhmeQId@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