public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Ulrich Hecht <uli@fpond.eu>
To: Pavel Machek <pavel@denx.de>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: Request for reviews for 4.4-st39, 4.4-cip74, 4.4-cip74-rt43
Date: Thu, 30 Mar 2023 13:43:49 +0200 (CEST)	[thread overview]
Message-ID: <585376205.1106587.1680176629311@webmail.strato.com> (raw)
In-Reply-To: <ZCVzQnoWvB/hIGnU@duo.ucw.cz>

Thanks for the reviews!

> On 03/30/2023 1:32 PM CEST Pavel Machek <pavel@denx.de> wrote:
>  | c075aa346 5d5aa2 o  | ARM: dts: exynos: Use Exynos5420
> 
> This one is wrong. Old compatible is used in
> drivers/phy/phy-exynos-mipi-video.c . Suggested new compatible is not
> used anywhere, so this would break things.
> 
>  | 9acadaf26 a98fc2    | staging: rtl8192e: Remove function ..dm_check_ac_dc_power calling a script
>  | 1c4293ded fe413a    | staging: rtl8192e: Remove call_usermodehelper starting RadioPower.sh
> 
> I'd not bother with staging stuff. Plus, these are not really
> bugfixes, they are really cleanups. I'd suggest we drop these.

I'll drop all of those then.

> > Not completely trivial backports, and/or stuff that touches important subsystems:
> > 
> a | 4e3b4b170 9a5571 o+ | f2fs: fix information leak in f2fs_move_inline_dirents()
> a | 5621f7a81 256fe4 o  | udf: Do not update file length for failed writes to inline files
> I assume this is preparation for next patch? | 11790a4fa b06730 o+ | irqdomain: Fix association race

It's also a fix for a tiny bug in its own right.

> a | 30b560087 3f883c o+ | irqdomain: Fix disassociation race

CU
Uli


  reply	other threads:[~2023-03-30 11:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  8:52 Request for reviews for 4.4-st39, 4.4-cip74, 4.4-cip74-rt43 Ulrich Hecht
2023-03-30 11:32 ` Pavel Machek
2023-03-30 11:43   ` Ulrich Hecht [this message]
2023-03-31 15:55     ` Alexander Grund
2023-04-03  8:56       ` [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=585376205.1106587.1680176629311@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