On Thu, Mar 06, 2025 at 10:14:55PM -0800, Matthew Brost wrote: > On Thu, Mar 06, 2025 at 02:32:56PM +0100, Greg Kroah-Hartman wrote: > > On Wed, Mar 05, 2025 at 08:29:08PM -0800, Matthew Brost wrote: > > > On Wed, Mar 05, 2025 at 06:48:07PM +0100, Greg Kroah-Hartman wrote: > > > > 6.12-stable review patch. If anyone has any objections, please let me know. > > > > > > > > > > We just got CI report on this patch, can you please hold off on backporting this. > > > > Ok, but note you all better revert this upstream as well soon, otherwise > > our tools have a tendancy to want to drag stuff like this back into > > stable kernels to remain in sync with Linus's tree. > > > > Thank you for the information on the workflow for issues like this. > > I'm pretty sure the follow-up in [1] will fix this and be merged any > minute now—I just saw this email after reviewing [1]. Is the correct > flow here to let the tools pick up the original offending patch and the > subsequent fix, or is there something else we should do? Please advise. Please let us know when the fix hits Linus's tree and what the git commit ids are that should be added to the stable tree at that time. thanks, greg k-h
