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-st58, 4.4-cip93
Date: Tue, 19 Nov 2024 20:48:53 +0100 [thread overview]
Message-ID: <Zzzrpf04NccFxosX@duo.ucw.cz> (raw)
In-Reply-To: <1048687374.465216.1731913250080@webmail.strato.de>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Hi!
> Here's the manual backports to review for the next 4.4 release which, as always, 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
>
Thanks for series, most look good (and I'm still reviewing them), but
I have few comments:
> 58779420cf48b netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
Ported patch is very different from what mainline has and changelog
describes. We probably don't have good way to handle this, maybe we
should have fixes-same-bug-as: xxx header or something like that.
> 0994d75c1648c kthread: add kthread_work tracepoints
These are simply added tracepoints. I guess they can be useful, but
I'd hardly call it a bug when they are not there.
> cad9f4314a05e drm/rockchip: vop: Allow 4096px width scaling
I guess noone uses this in 4.4, but this simply enables wider range of
configurations, and I'm pretty sure noone tested 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 --]
next prev parent reply other threads:[~2024-11-19 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 7:00 Request for reviews for 4.4-st58, 4.4-cip93 Ulrich Hecht
2024-11-19 19:48 ` Pavel Machek [this message]
2024-11-25 5:06 ` nobuhiro1.iwamatsu
2024-11-25 6:03 ` [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=Zzzrpf04NccFxosX@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