From: Jan Kara <jack@suse.cz>
To: Ritesh Harjani <ritesh.list@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Disha Goel <disgoel@linux.ibm.com>, Ted Tso <tytso@mit.edu>
Subject: Re: [PATCHv6 0/9] ext2: DIO to use iomap
Date: Mon, 24 Apr 2023 11:44:58 +0200 [thread overview]
Message-ID: <20230424094458.baigjp3pembjti4f@quack3> (raw)
In-Reply-To: <87edodigo4.fsf@doe.com>
On Fri 21-04-23 17:35:47, Ritesh Harjani wrote:
> Jan Kara <jack@suse.cz> writes:
> > them. The series has an ext4 cleanup (patch 3) and three iomap patches
>
> Also Patch-3 is on top of ext4 journalled data patch series of yours,
> otheriwse we might see a minor merge conflict.
>
> https://lore.kernel.org/all/20230329154950.19720-6-jack@suse.cz/
Yes, I have noticed :)
> > I guess I won't rush this for the coming merge window (unless Linus decides
> > to do rc8) but once we settle on the merge strategy I'll push out some
>
> Ok.
>
> > branch on which we can base further ext2 iomap conversion work.
> >
>
> Sure, will this branch also gets reflected in linux-next for wider testing?
Yes, the branch I'll push the ext2+ext4 patches to will be included in
linux-next (I'll merge it to for-next branch).
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2023-04-24 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 9:46 [PATCHv6 0/9] ext2: DIO to use iomap Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 1/9] ext2/dax: Fix ext2_setsize when len is page aligned Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 2/9] fs/buffer.c: Add generic_buffers_fsync*() implementation Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 3/9] ext4: Use generic_buffers_fsync_noflush() implementation Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 4/9] ext2: Use generic_buffers_fsync() implementation Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 5/9] ext2: Move direct-io to use iomap Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 6/9] fs.h: Add TRACE_IOCB_STRINGS for use in trace points Ritesh Harjani (IBM)
2023-04-21 15:56 ` Darrick J. Wong
2023-04-21 9:46 ` [PATCHv6 7/9] ext2: Add direct-io " Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 8/9] iomap: Remove IOMAP_DIO_NOSYNC unused dio flag Ritesh Harjani (IBM)
2023-04-21 15:56 ` Darrick J. Wong
2023-04-21 9:46 ` [PATCHv6 9/9] iomap: Add DIO tracepoints Ritesh Harjani (IBM)
2023-04-21 15:56 ` Darrick J. Wong
2023-04-21 11:23 ` [PATCHv6 0/9] ext2: DIO to use iomap Jan Kara
2023-04-21 12:05 ` Ritesh Harjani
2023-04-21 15:40 ` Darrick J. Wong
2023-04-24 9:43 ` Jan Kara
2023-04-24 9:44 ` Jan Kara [this message]
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=20230424094458.baigjp3pembjti4f@quack3 \
--to=jack@suse.cz \
--cc=disgoel@linux.ibm.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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