mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] xfs: fixes for 5.18-rc5
Date: Thu, 28 Apr 2022 16:19:21 +1000	[thread overview]
Message-ID: <20220428061921.GS1098723@dread.disaster.area> (raw)

Hi Linus,

Can you please pull the XFS fixes in the request attached below?
It's all minor stuff;  a 5.18 build regession fix, a deadlock fix
and an update to remove redundant fields from the XFS entry in the
MAINTAINERS file.

I just did a test merge against your current master branch and
didn't see any unexpected issues. It's been a while since I sent you
one of these things, so there's every chance I've missed something
I'm supposed to do now. If there's anything you notice that is even
slightly dodgy please let me know and I'll make sure it doesn't
happen next time.

-Dave.

The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:

  Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.18-fixes-1

for you to fetch changes up to 9a5280b312e2e7898b6397b2ca3cfd03f67d7be1:

  xfs: reorder iunlink remove operation in xfs_ifree (2022-04-21 08:45:16 +1000)

----------------------------------------------------------------
xfs: fixes for v5.18-rc5

XFS changes for v5.18-rc5:
- define buffer bit flags as unsigned to fix gcc-5 + c11 warnings
- remove redundant XFS fields from MAINTAINERS
- fix inode buffer locking order regression

----------------------------------------------------------------
Dave Chinner (2):
      xfs: convert buffer flags to unsigned.
      xfs: reorder iunlink remove operation in xfs_ifree

Tiezhu Yang (1):
      MAINTAINERS: update IOMAP FILESYSTEM LIBRARY and XFS FILESYSTEM

 MAINTAINERS        |  3 ---
 fs/xfs/xfs_buf.c   |  6 +++---
 fs/xfs/xfs_buf.h   | 42 +++++++++++++++++++++---------------------
 fs/xfs/xfs_inode.c | 24 +++++++++++++-----------
 fs/xfs/xfs_trans.h |  2 +-
 5 files changed, 38 insertions(+), 39 deletions(-)

-- 
Dave Chinner
david@fromorbit.com

             reply	other threads:[~2022-04-28  6:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  6:19 Dave Chinner [this message]
2022-04-28 16:46 ` Linus Torvalds
2022-04-28 21:31   ` Dave Chinner
2022-04-28 18:16 ` 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=20220428061921.GS1098723@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®