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>,
	"nobuhiro1.iwamatsu@toshiba.co.jp"
	<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: Request for review for 4.4-st69, 4.4-cip104
Date: Tue, 28 Oct 2025 22:08:07 +0100	[thread overview]
Message-ID: <aQEwt1csuBOZNtpd@duo.ucw.cz> (raw)
In-Reply-To: <1483065062.11009.1761645498941@webmail.strato.de>

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

Hi!

> Here are 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
> 
a > d019e4ada7f80 mmc: mvsdio: Fix dma_unmap_sg() nents value
a just a robustness > 86d6a790a96af i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path
a just an interface tweak > 67a69099af991 igb: fix link test skipping when interface is admin down
a just a LOCKDEP fix, not a minimum one > caeb615c0f733 net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod.
a > c7cf401d1bffb fbcon: fix integer overflow in fbcon_do_set_font
a > 1bdd492e312c1 ocfs2: fix recursive semaphore deadlock in fiemap call
a > 9ba58127984b1 e1000e: fix heap overflow in e1000_set_eeprom
> 
> Thanks for having a look.

Thank you, patches look good to me.

Best regards,
								Pavel
-- 
In cooperation with DENX Software Engineering GmbH, 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-10-28 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28  9:58 Request for review for 4.4-st69, 4.4-cip104 Ulrich Hecht
2025-10-28 21:08 ` Pavel Machek [this message]
2025-10-29  9:15 ` nobuhiro.iwamatsu.x90
2025-10-29 11:06   ` [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=aQEwt1csuBOZNtpd@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