public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: chandanbabu@kernel.org
Cc: cmaiolino@redhat.com,dchinner@redhat.com,djwong@kernel.org,hch@lst.de,kch@nvidia.com,leo.lilong@huawei.com,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org,sshegde@linux.ibm.com
Subject: [ANNOUNCE] xfs-linux: for-next updated to 49c379d3a72a
Date: Mon, 19 Feb 2024 20:28:33 +0530	[thread overview]
Message-ID: <87edd8wl4f.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)

Hi folks,

The for-next branch of the xfs-linux repository at:

	https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git

has just been updated.

Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update.

The new head of the for-next branch is commit:

49c379d3a72a xfs: use kvfree for buf in xfs_ioc_getbmap

I have now dropped previously merged "put the xfs xfile abstraction on a diet"
patchset.

16 new commits:

Christoph Hellwig (1):
      [49c379d3a72a] xfs: use kvfree for buf in xfs_ioc_getbmap

Darrick J. Wong (1):
      [1149314a16f7] xfs: disable sparse inode chunk alignment check when there is no alignment

Dave Chinner (12):
      [10634530f7ba] xfs: convert kmem_zalloc() to kzalloc()
      [f078d4ea8276] xfs: convert kmem_alloc() to kmalloc()
      [afdc115559c5] xfs: move kmem_to_page()
      [49292576136f] xfs: convert kmem_free() for kvmalloc users to kvfree()
      [d4c75a1b40cd] xfs: convert remaining kmem_free() to kfree()
      [178231af2bdc] xfs: use an empty transaction for fstrim
      [94a69db2367e] xfs: use __GFP_NOLOCKDEP instead of GFP_NOFS
      [0b3a76e955eb] xfs: use GFP_KERNEL in pure transaction contexts
      [2c1e31ed5c88] xfs: place intent recovery under NOFS allocation context
      [c704ecb2410e] xfs: place the CIL under nofs allocation context
      [204fae32d5f7] xfs: clean up remaining GFP_NOFS users
      [57b98393b812] xfs: use xfs_defer_alloc a bit more

Long Li (1):
      [e4c3b72a6ea9] xfs: ensure submit buffers on LSN boundaries in error handlers

Shrikanth Hegde (1):
      [0164defd0d86] xfs: remove duplicate ifdefs

Code Diffstat:

 fs/xfs/Makefile                   |   3 +-
 fs/xfs/kmem.c                     |  30 ------
 fs/xfs/kmem.h                     |  83 ---------------
 fs/xfs/libxfs/xfs_ag.c            |  10 +-
 fs/xfs/libxfs/xfs_attr.c          |   3 +-
 fs/xfs/libxfs/xfs_attr_leaf.c     |  18 ++--
 fs/xfs/libxfs/xfs_bmap.c          |   2 +-
 fs/xfs/libxfs/xfs_btree.c         |   2 +-
 fs/xfs/libxfs/xfs_btree.h         |   4 +-
 fs/xfs/libxfs/xfs_btree_staging.c |  10 +-
 fs/xfs/libxfs/xfs_da_btree.c      |  22 ++--
 fs/xfs/libxfs/xfs_defer.c         |  23 ++---
 fs/xfs/libxfs/xfs_dir2.c          |  48 ++++-----
 fs/xfs/libxfs/xfs_dir2_block.c    |   6 +-
 fs/xfs/libxfs/xfs_dir2_sf.c       |  16 +--
 fs/xfs/libxfs/xfs_iext_tree.c     |  26 +++--
 fs/xfs/libxfs/xfs_inode_fork.c    |  29 +++---
 fs/xfs/libxfs/xfs_refcount.c      |   2 +-
 fs/xfs/libxfs/xfs_rmap.c          |   2 +-
 fs/xfs/scrub/cow_repair.c         |   2 +-
 fs/xfs/scrub/ialloc_repair.c      |   2 +-
 fs/xfs/xfs_acl.c                  |   4 +-
 fs/xfs/xfs_attr_item.c            |  14 +--
 fs/xfs/xfs_attr_list.c            |   6 +-
 fs/xfs/xfs_bmap_item.c            |   7 +-
 fs/xfs/xfs_bmap_util.c            |   2 +-
 fs/xfs/xfs_buf.c                  |  48 +++++----
 fs/xfs/xfs_buf_item.c             |   8 +-
 fs/xfs/xfs_buf_item_recover.c     |   8 +-
 fs/xfs/xfs_discard.c              |  17 +++-
 fs/xfs/xfs_dquot.c                |   2 +-
 fs/xfs/xfs_error.c                |   8 +-
 fs/xfs/xfs_extent_busy.c          |   5 +-
 fs/xfs/xfs_extfree_item.c         |   8 +-
 fs/xfs/xfs_filestream.c           |   6 +-
 fs/xfs/xfs_icache.c               |   5 +-
 fs/xfs/xfs_icreate_item.c         |   2 +-
 fs/xfs/xfs_inode.c                |   4 +-
 fs/xfs/xfs_inode_item.c           |   2 +-
 fs/xfs/xfs_inode_item_recover.c   |   5 +-
 fs/xfs/xfs_ioctl.c                |   8 +-
 fs/xfs/xfs_iops.c                 |   2 +-
 fs/xfs/xfs_itable.c               |  12 +--
 fs/xfs/xfs_iwalk.c                |   9 +-
 fs/xfs/xfs_linux.h                |  14 ++-
 fs/xfs/xfs_log.c                  |  20 ++--
 fs/xfs/xfs_log_cil.c              |  31 ++++--
 fs/xfs/xfs_log_recover.c          | 101 ++++++++++++-------
 fs/xfs/xfs_mount.c                |   2 +-
 fs/xfs/xfs_mru_cache.c            |  17 ++--
 fs/xfs/xfs_qm.c                   |  18 ++--
 fs/xfs/xfs_refcount_item.c        |  12 +--
 fs/xfs/xfs_rmap_item.c            |  11 +-
 fs/xfs/xfs_rtalloc.c              |  10 +-
 fs/xfs/xfs_super.c                |   4 +-
 fs/xfs/xfs_sysfs.c                |   4 -
 fs/xfs/xfs_trace.h                |  25 -----
 fs/xfs/xfs_trans_ail.c            |   7 +-
 58 files changed, 373 insertions(+), 438 deletions(-)
 delete mode 100644 fs/xfs/kmem.c
 delete mode 100644 fs/xfs/kmem.h

                 reply	other threads:[~2024-02-19 15:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87edd8wl4f.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=cmaiolino@redhat.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=kch@nvidia.com \
    --cc=leo.lilong@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sshegde@linux.ibm.com \
    /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