linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
	Jingbo Xu <jefflexu@linux.alibaba.com>, Chao Yu <chao@kernel.org>,
	Yue Hu <huyue2@coolpad.com>, Tiwei Bie <tiwei.btw@antgroup.com>
Subject: [GIT PULL] erofs updates for 6.7-rc1
Date: Wed, 1 Nov 2023 12:35:44 +0800	[thread overview]
Message-ID: <ZUHVoP/682uPjvfj@debian> (raw)

Hi Linus,

Could you consider this pull request for 6.7-rc1?

Nothing exciting lands for this cycle, since we're still busying in
developing support for sub-page blocks and large-folios of
compressed data for new scenarios on Android.

In this cycle, MicroLZMA format is marked as stable, and there are
minor cleanups around documentation and codebase.  In addition, it
also fixes incorrect lockref usage in erofs_insert_workgroup().

All commits have been in -next and no potential merge conflict is
observed.

Thanks,
Gao Xiang

The following changes since commit 94f6f0550c625fab1f373bb86a6669b45e9748b3:

  Linux 6.6-rc5 (2023-10-08 13:49:43 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.7-rc1

for you to fetch changes up to 1a0ac8bd7a4fa5b2f4ef14c3b1e9d6e5a5faae06:

  erofs: fix erofs_insert_workgroup() lockref usage (2023-10-31 18:59:49 +0800)

----------------------------------------------------------------
Changes since last update:

 - Fix inode metadata space layout documentation;

 - Avoid warning MicroLZMA format anymore;

 - Fix erofs_insert_workgroup() lockref usage;

 - Some cleanups.

----------------------------------------------------------------
Ferry Meng (2):
      erofs: get rid of ROOT_NID()
      erofs: tidy up redundant includes

Gao Xiang (3):
      erofs: don't warn MicroLZMA format anymore
      erofs: simplify compression configuration parser
      erofs: fix erofs_insert_workgroup() lockref usage

Tiwei Bie (1):
      erofs: fix inode metadata space layout description in documentation

 Documentation/filesystems/erofs.rst |  2 +-
 fs/erofs/Kconfig                    |  7 +---
 fs/erofs/compress.h                 |  6 +++
 fs/erofs/data.c                     |  2 -
 fs/erofs/decompressor.c             | 63 +++++++++++++++++++++++++++--
 fs/erofs/decompressor_deflate.c     |  6 +--
 fs/erofs/decompressor_lzma.c        |  7 +---
 fs/erofs/internal.h                 | 42 ++-----------------
 fs/erofs/super.c                    | 81 +++++--------------------------------
 fs/erofs/utils.c                    |  8 +---
 fs/erofs/zdata.c                    |  1 +
 11 files changed, 89 insertions(+), 136 deletions(-)

             reply	other threads:[~2023-11-01  4:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  4:35 Gao Xiang [this message]
2023-11-02 18:37 ` [GIT PULL] erofs updates for 6.7-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=ZUHVoP/682uPjvfj@debian \
    --to=xiang@kernel.org \
    --cc=chao@kernel.org \
    --cc=huyue2@coolpad.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwei.btw@antgroup.com \
    --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).