public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Ulrich Hecht <uli@fpond.eu>
To: pavel@nabladev.com
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"nobuhiro.iwamatsu.x90@mail.toshiba"
	<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Re: [cip-dev] Request for review for 4.4-st73, 4.4-cip108
Date: Tue, 3 Mar 2026 03:18:56 +0100 (CET)	[thread overview]
Message-ID: <215520992.150669.1772504336203@webmail.strato.de> (raw)
In-Reply-To: <aaAo8TUKFDgI9j+f@duo.ucw.cz>


> On 02/26/2026 12:05 PM CET Pavel Machek via lists.cip-project.org <pavel=nabladev.com@lists.cip-project.org> wrote:
> 
>  
> 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 > dd2af1ff15baa macvlan: fix possible UAF in macvlan_forward_source()
> a > 6e7f9685b9d35 wifi: wlcore: ensure skb headroom before skb_push
> a > 1b847006e7141 sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT
> a> bf3c650dfddf3 btrfs: fix deadlock in wait_current_trans() due to ignored transaction type
> a> 9dbc25309be1c net/sched: sch_qfq: do not free existing class in qfq_change_class()
> >
> 
> Thank you, these look good to me.

Thanks!

> > Plus one fix for my convenience:
> > 
> > e0e89cfcf08df arm64: replace Sun/Solaris style flag on section directive
> 
> Pointer "mainline equivalent of this is XXX" would be nice here.

Normally yes, but in this case there is none. The offending line disappeared organically during post-4.4 mainline development before it could become an issue there.

CU
Uli


  reply	other threads:[~2026-03-03  2:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  5:32 Request for review for 4.4-st73, 4.4-cip108 Ulrich Hecht
2026-02-26 11:05 ` Pavel Machek
2026-03-03  2:18   ` Ulrich Hecht [this message]
2026-02-27  6:50 ` nobuhiro.iwamatsu.x90

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=215520992.150669.1772504336203@webmail.strato.de \
    --to=uli@fpond.eu \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=pavel@nabladev.com \
    /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