From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: DMAPI ioctl housecleaning for 5.17-rc1
Date: Thu, 20 Jan 2022 10:20:39 -0800 [thread overview]
Message-ID: <20220120182039.GN13540@magnolia> (raw)
Hi Linus,
This is the first of a series of small pull requests that perform some
long overdue housecleaning of XFS ioctls. This first pull request
removes the FSSETDM ioctl, which was used to set DMAPI event attributes
on XFS files. The DMAPI support has never been merged upstream and the
implementation of FSSETDM itself was removed two years ago, so let's
withdraw it completely.
As usual, I did a test-merge with upstream master as of a few minutes
ago and didn't see any merge conflicts. Please let me know if you
encounter any problems.
--D
The following changes since commit 4a9bca86806fa6fc4fbccf050c1bd36a4778948a:
xfs: fix online fsck handling of v5 feature bits on secondary supers (2022-01-12 09:45:21 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.17-merge-4
for you to fetch changes up to 9dec0368b9640c09ef5af48214e097245e57a204:
xfs: remove the XFS_IOC_FSSETDM definitions (2022-01-17 09:16:40 -0800)
----------------------------------------------------------------
Withdraw the ioctl definition for the FSSETDM ioctl.
----------------------------------------------------------------
Darrick J. Wong (1):
xfs: remove the XFS_IOC_FSSETDM definitions
fs/xfs/libxfs/xfs_fs.h | 29 ++++-------------------------
1 file changed, 4 insertions(+), 25 deletions(-)
next reply other threads:[~2022-01-20 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 18:20 Darrick J. Wong [this message]
2022-01-21 6:56 ` [GIT PULL] xfs: DMAPI ioctl housecleaning for 5.17-rc1 pr-tracker-bot
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=20220120182039.GN13540@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).