linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@sandeen.net>
Subject: [GIT PULL] xfs: fixes for 4.15
Date: Fri, 17 Nov 2017 11:46:45 -0800	[thread overview]
Message-ID: <20171117194645.GN5119@magnolia> (raw)
In-Reply-To: <20171114014954.GF25227@magnolia>

Hi Linus,

Here are a couple more patches to fix a locking bug and some inconsistent
type usage in some of the new code.

--D

The following changes since commit abc36be236358162202e86ad88616ff95a755101:

  Merge tag 'configfs-for-4.15' of git://git.infradead.org/users/hch/configfs (2017-11-14 14:44:04 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.15-merge-2

for you to fetch changes up to 2015a63dce8d73a439232a0d5162c88d8513101e:

  xfs: fix type usage (2017-11-16 12:06:45 -0800)

----------------------------------------------------------------
Changes since last update:
- Fix a forgotten rcu read unlock
- Fix some inconsistent integer type usage.

----------------------------------------------------------------
Darrick J. Wong (2):
      xfs: fix forgotten rcu read unlock when skipping inode reclaim
      xfs: fix type usage

 fs/xfs/libxfs/xfs_iext_tree.c  | 2 +-
 fs/xfs/libxfs/xfs_log_format.h | 4 ++--
 fs/xfs/xfs_inode.c             | 1 +
 3 files changed, 4 insertions(+), 3 deletions(-)

      reply	other threads:[~2017-11-17 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14  1:49 [GIT PULL] xfs: great scads of new stuff for 4.15 Darrick J. Wong
2017-11-17 19:46 ` Darrick J. Wong [this message]

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=20171117194645.GN5119@magnolia \
    --to=djwong@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).