From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Theodore Ts'o <tytso@mit.edu>
Cc: Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Vishal Moola (Oracle)" <vishal.moola@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: linux-next: manual merge of the mm-stable tree with the ext4 tree
Date: Fri, 24 Feb 2023 09:42:49 +0700 [thread overview]
Message-ID: <5f228150-0e29-6d58-3dcf-776bc2a630b7@gmail.com> (raw)
In-Reply-To: <20230223144722.635ab483@canb.auug.org.au>
On 2/23/23 10:47, Stephen Rothwell wrote:
> I still have not been able to figure out a merge resolution for this,
> so the ext4 tree still has had no testing in linux-next and the merge
> window is progressing. Does anyone want to help with this?
>
I think at worst, Linus will have to resolve this mess himself when PR
for ext4 is submitted and merged in this merge window.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-02-24 2:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 4:29 linux-next: manual merge of the mm-stable tree with the ext4 tree Stephen Rothwell
2023-02-20 14:27 ` Matthew Wilcox
2023-02-21 6:54 ` Stephen Rothwell
2023-02-23 3:47 ` Stephen Rothwell
2023-02-24 2:42 ` Bagas Sanjaya [this message]
2023-02-24 5:11 ` Stephen Rothwell
2023-02-24 6:08 ` Linus Torvalds
2023-02-24 22:20 ` Theodore Ts'o
2023-02-24 23:01 ` Linus Torvalds
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=5f228150-0e29-6d58-3dcf-776bc2a630b7@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vishal.moola@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox