[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fcMPe6V9vMYxkXRMnKXiaeTnOwAMBNRTmF1mgLePTpz3Q4hPqpb0WVQ5aXZljqkOtZ2W_47PVL1Q4lnf7kZJhFS4aGwP8_4QiqJl2ScKSi4=@proton.me>
Date: Wed, 26 Nov 2025 03:18:48 +0000
From: incogcyberpunk@...ton.me
To: patchwork-bot+bluetooth@...nel.org
Cc: Doug Anderson <dianders@...omium.org>, marcel@...tmann.org, luiz.dentz@...il.com, 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
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.
Regards,
IncogCyberpunk
Powered by blists - more mailing lists