From: Ulrich Hecht <uli@fpond.eu>
To: cip-dev@lists.cip-project.org, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] 4.4 steps towards release
Date: Wed, 18 Jan 2023 06:57:14 +0100 (CET) [thread overview]
Message-ID: <1038288592.1739244.1674021434811@webmail.strato.com> (raw)
In-Reply-To: <Y8cKLnKsp+jiHUna@duo.ucw.cz>
> On 01/17/2023 9:50 PM CET Pavel Machek <pavel@denx.de> wrote:
> And these look okay to me, too.
Thank you very much. I have since included the few remaining patches from the final 4.9.377 release. There is one trivial backport in it that I'm mentioning here for the record:
** m | 0588b12c4 6b0d04 o+ | media: dvb-core: Fix double free in dvb_register_device()
I have also added a fix for CVE-2023-0047 that is in 4.9.291, but for reasons unknown to me wasn't backported to 4.4 before we took over:
39bdf0444b238 mm, oom: do not trigger out_of_memory from the #PF
CU
Uli
prev parent reply other threads:[~2023-01-18 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 15:53 4.4 steps towards release Pavel Machek
2023-01-10 8:14 ` [cip-dev] " Ulrich Hecht
2023-01-15 22:09 ` Pavel Machek
2023-01-16 1:08 ` Ulrich Hecht
2023-01-17 20:50 ` Pavel Machek
2023-01-18 5:57 ` Ulrich Hecht [this message]
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=1038288592.1739244.1674021434811@webmail.strato.com \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@denx.de \
/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