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: fixes for 5.17-rc1
Date: Fri, 21 Jan 2022 17:08:07 -0800 [thread overview]
Message-ID: <20220122010807.GT13540@magnolia> (raw)
Hi Linus,
Please pull this branch of minor corrections for 5.17-rc1. One of the
patches removes some dead code from xfs_ioctl32.h and the other fixes
broken workqueue flushing in the inode garbage collector.
As usual, I did a test-merge with upstream master as of a few minutes
ago, and didn't see any conflicts. Please let me know if you encounter
any problems.
--D
The following changes since commit b3bb9413e717b44e4aea833d07f14e90fb91cf97:
xfs: remove the XFS_IOC_{ALLOC,FREE}SP* definitions (2022-01-17 09:17:11 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.17-merge-7
for you to fetch changes up to 6191cf3ad59fda5901160633fef8e41b064a5246:
xfs: flush inodegc workqueue tasks before cancel (2022-01-19 14:58:26 -0800)
----------------------------------------------------------------
New code for 5.17:
- Minor cleanup of ioctl32 cruft
- Clean up open coded inodegc workqueue function calls
----------------------------------------------------------------
Brian Foster (1):
xfs: flush inodegc workqueue tasks before cancel
Darrick J. Wong (1):
xfs: remove unused xfs_ioctl32.h declarations
fs/xfs/xfs_icache.c | 22 ++++------------------
fs/xfs/xfs_ioctl32.h | 18 ------------------
2 files changed, 4 insertions(+), 36 deletions(-)
next reply other threads:[~2022-01-22 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 1:08 Darrick J. Wong [this message]
2022-01-22 9:40 ` [GIT PULL] xfs: fixes 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=20220122010807.GT13540@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