From: Christoph Hellwig <hch@lst.de>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: Dave Chinner <dchinner@redhat.com>,
abaci@linux.alibaba.com, allison.henderson@oracle.com,
catherine.hoang@oracle.com, dan.carpenter@linaro.org,
djwong@kernel.org, hch@lst.de, jiapeng.chong@linux.alibaba.com,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
thorsten.blum@toblux.com
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to c414a87ff750
Date: Mon, 22 Apr 2024 07:55:12 +0200 [thread overview]
Message-ID: <20240422055512.GA2486@lst.de> (raw)
In-Reply-To: <87jzkqlzbr.fsf@debian-BULLSEYE-live-builder-AMD64>
On Mon, Apr 22, 2024 at 11:16:13AM +0530, Chandan Babu R wrote:
> Christoph, Can you please rebase and re-post the following patchsets on top of
> xfs-linux's updated for-next branch,
> 1. xfs: compile out v4 support if disabled
> 2. spring cleaning for xfs_extent_busy_clear
> 3. bring back RT delalloc support
Can you please drop this one first:
> [6279a2050c8b] xfs: fix sparse warning in xfs_extent_busy_clear
befoere I resend series 2 above?
It is the inital hack for the sparse warnings and extent busy sparse
warnings, which just causes a lot of churn.
next prev parent reply other threads:[~2024-04-22 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 5:46 [ANNOUNCE] xfs-linux: for-next updated to c414a87ff750 Chandan Babu R
2024-04-22 5:55 ` Christoph Hellwig [this message]
2024-04-22 8:47 ` Chandan Babu R
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=20240422055512.GA2486@lst.de \
--to=hch@lst.de \
--cc=abaci@linux.alibaba.com \
--cc=allison.henderson@oracle.com \
--cc=catherine.hoang@oracle.com \
--cc=chandanbabu@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=thorsten.blum@toblux.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.