Christoph Hellwig
2023-Jan-10 15:32 UTC
[Ocfs2-devel] remove write_one_page / folio_write_one
On Tue, Jan 10, 2023 at 02:00:42PM +0100, David Sterba wrote:> On Tue, Jan 10, 2023 at 09:16:53AM +0100, Christoph Hellwig wrote: > > On Mon, Jan 09, 2023 at 08:53:09PM +0100, David Sterba wrote: > > > The btrfs patches were sent separately some time ago, now merged to > > > misc-next with updated changelogs and with the suggested switch to folio > > > API in the 2nd patch. > > > > Yes, 7 weeks ago to be exact. I wish we could just feed everything > > together now that we've missed the previous merge window, as that > > makes patch juggling for Andrew and Matthew a lot simpler. > > The patches are not fixes so they should wait for the next merge window.Agreed. But it would be a lot simpler if we could queue them up in -mm with the other patches now that we've missed the previous merge window.
On Tue, Jan 10, 2023 at 04:32:16PM +0100, Christoph Hellwig wrote:> On Tue, Jan 10, 2023 at 02:00:42PM +0100, David Sterba wrote: > > On Tue, Jan 10, 2023 at 09:16:53AM +0100, Christoph Hellwig wrote: > > > On Mon, Jan 09, 2023 at 08:53:09PM +0100, David Sterba wrote: > > > > The btrfs patches were sent separately some time ago, now merged to > > > > misc-next with updated changelogs and with the suggested switch to folio > > > > API in the 2nd patch. > > > > > > Yes, 7 weeks ago to be exact. I wish we could just feed everything > > > together now that we've missed the previous merge window, as that > > > makes patch juggling for Andrew and Matthew a lot simpler. > > > > The patches are not fixes so they should wait for the next merge window. > > Agreed. But it would be a lot simpler if we could queue them up in > -mm with the other patches now that we've missed the previous merge > window.Ok then, to make it easier for the folio changes I'll send the two btrfs patches next week. As the rest of the series does not depend on it, I don't see the need to let them all go via the mm tree.