[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABBYNZ+LrMOr-Bb-Sfk--FAHjMWxzeUCdDoGLuRqhF99xaGE3A@mail.gmail.com>
Date: Tue, 25 Nov 2025 22:29:06 -0500
From: Luiz Augusto von Dentz <luiz.dentz@...il.com>
To: incogcyberpunk@...ton.me
Cc: patchwork-bot+bluetooth@...nel.org, Doug Anderson <dianders@...omium.org>,
marcel@...tmann.org, matthias.bgg@...il.com,
angelogioacchino.delregno@...labora.com, regressions@...mhuis.info,
regressions@...ts.linux.dev, johan.hedberg@...il.com, sean.wang@...iatek.com,
stable@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v3] Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf()
NULL deref
Hi,
On Tue, Nov 25, 2025 at 10:18 PM <incogcyberpunk@...ton.me> wrote:
>
> Hey,
>
> It's been almost a week since the regression was reported and an patch was provided to fix the issue, which has now been accepted in the linux-next tree; but I see that despite being a patch for regression, a merge/pull request was not made upstream for the latest -rc mainline release.
>
> Is there any way that I can track the updates for this patch to be onto the mainline release?
>
> Sorry, if I am missing anything.
This was merged into net tree a few days ago:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8a4dfa8fa6b5
So it should get into Linus tree in the next few days.
> Regards,
> IncogCyberpunk
--
Luiz Augusto von Dentz
Powered by blists - more mailing lists