On Mon, Jul 24, 2023 at 04:49:16PM +0200, Jann Horn wrote: > On Fri, Jul 14, 2023 at 5:34 AM Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > > On Thu, Jul 13, 2023 at 08:02:12PM -0700, Suren Baghdasaryan wrote: > > > On Tue, Jul 11, 2023 at 1:21 PM Matthew Wilcox (Oracle) > > > <willy@xxxxxxxxxxxxx> wrote: > > > > > > > > This reverts commit 7a7f094635349a7d0314364ad50bdeb770b6df4f. > > > > > > nit: some explanation and SOB would be nice. > > > > Well, it can't be actually applied. What needs to happen is that the > > networking people need to drop the commit from their tree. Some review > > from the networking people would be helpful to be sure that I didn't > > break anything in my reworking of this patch to apply after my patches. > > Are you saying you want them to revert it before it reaches mainline? > That commit landed in v6.5-rc1. ... what? It was posted on June 16th. How does it end up in rc1 on July 9th? 6.4 was June 25th. 9 days is long enough for something that's not an urgent fix to land in rc1? Networking doesn't close development at rc5/6 like most subsystem trees?
