All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@rothwell.id.au>
To: Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Matthew Wilcox <willy@infradead.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	ext4 Development <linux-ext4@vger.kernel.org>
Subject: Re: The state of ext4 tree merging (was Re: Linux 6.3-rc1)
Date: Tue, 7 Mar 2023 09:02:03 +1100	[thread overview]
Message-ID: <20230307090203.56c41488@oak.ozlabs.ibm.com> (raw)
In-Reply-To: <20230306124134.hmeuvjhihs4ubpmz@quack3>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Hi all,

On Mon, 6 Mar 2023 13:41:34 +0100 Jan Kara <jack@suse.cz> wrote:
>
> To be fair, the data=journal cleanups got held back only partially due to
> the merge issues. Another problem is that they somehow make problems with
> filesystem freezing in data=journal mode more frequent and we wanted to
> understand (and hopefully fix) that. Of course if Ted could look into this
> earlier or I could earlier debug these issues, we could have merged the
> cleanups but that's always the case that you have to prioritize and these
> cleanups don't have that high priority...

In that case, it would be nice (for me at least) if the ext4 tree was
now reset to be v6.3-rc1 i.e. get rid of the duplicate commits and the
new stuff that is still being worked on.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-03-06 22:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 23:24 Linux 6.3-rc1 Linus Torvalds
2023-03-06  1:41 ` linux-next: stats (Was: Linux 6.3-rc1) Stephen Rothwell
2023-03-06  3:17 ` The state of ext4 tree merging (was " Bagas Sanjaya
2023-03-06 12:41   ` Jan Kara
2023-03-06 22:02     ` Stephen Rothwell [this message]
2023-03-07 16:21       ` Theodore Ts'o
2023-03-07 20:45         ` Stephen Rothwell
2023-03-08  0:45           ` Theodore Ts'o
2023-03-06  8:20 ` Build regressions/improvements in v6.3-rc1 Geert Uytterhoeven
2023-03-06  8:42   ` Geert Uytterhoeven
2023-03-06  8:42     ` Geert Uytterhoeven
2023-03-06  8:42     ` Geert Uytterhoeven
2023-03-06 16:52 ` Linux 6.3-rc1 Guenter Roeck
2023-03-06 18:12   ` Linus Torvalds
2023-03-06 22:02   ` Guenter Roeck
2023-03-08 10:07 ` Luna Jernberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230307090203.56c41488@oak.ozlabs.ibm.com \
    --to=sfr@rothwell.id.au \
    --cc=akpm@linux-foundation.org \
    --cc=bagasdotme@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.