From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] GFS2 changes for 5.13
Date: Thu, 29 Apr 2021 12:34:45 +0200 [thread overview]
Message-ID: <20210429103445.846975-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 changes for 5.13.
Thanks a lot,
Andreas
The following changes since commit 8e29be3468d4565dd95fbb098df0d7a79ee60d71:
Merge tag 'gfs2-v5.12-rc2-fixes2' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2021-04-03 12:15:01 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-for-5.13
for you to fetch changes up to e5966cf20f0c7e40fd8c208ba1614e1a35a8deee:
gfs2: Fix fall-through warnings for Clang (2021-04-20 22:38:21 +0200)
----------------------------------------------------------------
Changes in gfs2:
- Fix some compiler and kernel-doc warnings.
- Various minor cleanups and optimizations.
- Add a new sysfs gfs2 status file with some filesystem wide
information.
----------------------------------------------------------------
Andreas Gruenbacher (7):
gfs2: Remove unused variable sb_format
gfs2: Add new gfs2_iomap_get helper
gfs2: Turn gfs2_extent_map into gfs2_{get,alloc}_extent
gfs2: Replace gfs2_lblk_to_dblk with gfs2_get_extent
gfs2: Turn gfs2_meta_indirect_buffer into gfs2_meta_buffer
gfs2: Silence possible null pointer dereference warning
gfs2: Make gfs2_setattr_simple static
Bob Peterson (4):
gfs2: don't create empty buffers for NO_CREATE
gfs2: Eliminate gh parameter from go_xmote_bh func
gfs2: Fix dir.c function parameter descriptions
gfs2: Add new sysfs file for gfs2 status
Gustavo A. R. Silva (1):
gfs2: Fix fall-through warnings for Clang
Lee Jones (1):
gfs2: Fix a number of kernel-doc warnings
fs/gfs2/aops.c | 5 +-
fs/gfs2/bmap.c | 153 ++++++++++++++++++++++++++-------------------------
fs/gfs2/bmap.h | 13 +++--
fs/gfs2/dir.c | 52 +++++++++--------
fs/gfs2/file.c | 12 ++--
fs/gfs2/glock.c | 12 ++--
fs/gfs2/glops.c | 16 ++----
fs/gfs2/incore.h | 3 +-
fs/gfs2/inode.c | 32 +++++------
fs/gfs2/inode.h | 1 -
fs/gfs2/lock_dlm.c | 37 +++++++------
fs/gfs2/log.c | 23 ++++----
fs/gfs2/lops.c | 13 +++--
fs/gfs2/meta_io.c | 20 ++++---
fs/gfs2/meta_io.h | 6 +-
fs/gfs2/ops_fstype.c | 8 +--
fs/gfs2/quota.c | 6 +-
fs/gfs2/recovery.c | 8 ++-
fs/gfs2/rgrp.c | 8 ++-
fs/gfs2/super.c | 12 ++--
fs/gfs2/sys.c | 67 ++++++++++++++++++++++
fs/gfs2/util.c | 19 ++++---
fs/gfs2/xattr.c | 29 +++-------
23 files changed, 312 insertions(+), 243 deletions(-)
next reply other threads:[~2021-04-29 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 10:34 Andreas Gruenbacher [this message]
2021-04-29 17:52 ` [GIT PULL] GFS2 changes for 5.13 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=20210429103445.846975-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).