From: Christoph Hellwig <hch@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: djwong@kernel.org, cem@kernel.org,
Long Li <leo.lilong@huawei.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
yi.zhang@huawei.com, houtao1@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH v6 0/3] iomap: fix zero padding data issue in concurrent append writes
Date: Tue, 10 Dec 2024 03:38:48 -0800 [thread overview]
Message-ID: <Z1goSBpgKTydaQAV@infradead.org> (raw)
In-Reply-To: <20241210-strecken-anbeginn-4c3af8c6abe8@brauner>
Can you please drop the third patch? We'll probably have something in
XFS that will conflict with it if not reabsed, so it's probably better
to merge it through the xfs tree so that everything can be properly
merged.
next prev parent reply other threads:[~2024-12-10 11:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 11:42 [PATCH v6 0/3] iomap: fix zero padding data issue in concurrent append writes Long Li
2024-12-09 11:42 ` [PATCH v6 1/3] iomap: pass byte granular end position to iomap_add_to_ioend Long Li
2024-12-09 14:06 ` Brian Foster
2024-12-10 8:09 ` Long Li
2024-12-10 11:50 ` Brian Foster
2024-12-09 11:42 ` [PATCH v6 2/3] iomap: fix zero padding data issue in concurrent append writes Long Li
2024-12-09 11:42 ` [PATCH v6 3/3] xfs: clean up xfs_end_ioend() to reuse local variables Long Li
2025-01-14 10:30 ` Carlos Maiolino
2024-12-10 10:15 ` [PATCH v6 0/3] iomap: fix zero padding data issue in concurrent append writes Christian Brauner
2024-12-10 11:38 ` Christoph Hellwig [this message]
2024-12-11 10:34 ` Christian Brauner
2024-12-11 10:09 ` (subset) " Christian Brauner
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=Z1goSBpgKTydaQAV@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=houtao1@huawei.com \
--cc=leo.lilong@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
/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