From: Chandan Babu R <chandanbabu@kernel.org>
To: ruansy.fnst@fujitsu.com
Cc: Christoph Hellwig <hch@lst.de>,
catherine.hoang@oracle.com, cheng.lin130@zte.com.cn,
dan.j.williams@intel.com, dchinner@redhat.com,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
osandov@fb.com, "Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to 22c2699cb068
Date: Tue, 31 Oct 2023 22:32:30 +0530 [thread overview]
Message-ID: <875y2mk9fo.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20231031164359.GA1041814@frogsfrogsfrogs>
On Tue, Oct 31, 2023 at 09:43:59 AM -0700, Darrick J. Wong wrote:
> On Tue, Oct 31, 2023 at 10:02:42AM +0100, Christoph Hellwig wrote:
>> Can you also pick up:
>>
>> "xfs: only remap the written blocks in xfs_reflink_end_cow_extent"
>>
>> ?
>>
>> Also this seems to a bit of a mix of fixes for 6.7 and big stuff that
>> is too late for the merge window.
>
> If by 'big stuff' you mean the MF_MEM_PRE_REMOVE patch, then yes, I
> agree that it's too late to be changing code outside xfs. Bumping that
> to 6.8 will disappoint Shiyang, regrettably.
>
I am sorry Shiyang, I will have to postpone your "mm, pmem, xfs: Introduce
MF_MEM_PRE_REMOVE for unbind" patch for v6.8. The delay was my
mistake. Apologies once again.
I have updated xfs-linux's for-next branch and I will be sending an
announcement shortly.
--
Chandan
next prev parent reply other threads:[~2023-10-31 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 5:46 [ANNOUNCE] xfs-linux: for-next updated to 22c2699cb068 Chandan Babu R
2023-10-30 5:46 ` Chandan Babu R
2023-10-31 9:02 ` Christoph Hellwig
2023-10-31 10:47 ` Chandan Babu R
2023-10-31 16:43 ` Darrick J. Wong
2023-10-31 17:02 ` Chandan Babu R [this message]
2023-11-01 11:30 ` Shiyang Ruan
2023-10-31 17:12 ` Christoph Hellwig
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=875y2mk9fo.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=cheng.lin130@zte.com.cn \
--cc=dan.j.williams@intel.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=osandov@fb.com \
--cc=ruansy.fnst@fujitsu.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 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.