Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [GIT PULL] ext2, reiserfs, udf, and quota cleanups and fixes for 6.4-rc1
Date: Tue, 25 Apr 2023 12:35:01 +0200	[thread overview]
Message-ID: <20230425103501.ib4qoy4j5a3mzf2c@quack3> (raw)

  Hello Linus,

  could you please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fs_for_v6.4-rc1

To get a couple of small fixes and cleanups for ext2, udf, reiserfs, and
quota. The biggest change in this pull is making CONFIG_PRINT_QUOTA_WARNING
depend on BROKEN with an outlook for removing it completely in an year or
so.

Top of the tree is 36d532d713db. The full shortlog is:

Colin Ian King (1):
      ext2: remove redundant assignment to pointer end

Jan Kara (3):
      ext2: Correct maximum ext2 filesystem block size
      ext2: Check block size validity during mount
      quota: Use register_sysctl_init() for registering fs_dqstats_table

Luis Chamberlain (1):
      quota: simplify two-level sysctl registration for fs_dqstats_table

Matthew Wilcox (Oracle) (1):
      udf: Use folios in udf_adinicb_writepage()

Tom Rix (2):
      reiserfs: remove unused sched_count variable
      reiserfs: remove unused iter variable

Yangtao Li (5):
      udf: use wrapper i_blocksize() in udf_discard_prealloc()
      quota: fixup *_write_file_info() to return proper error code
      quota: make dquot_set_dqinfo return errors from ->write_info
      quota: update Kconfig comment
      quota: mark PRINT_QUOTA_WARNING as BROKEN

The diffstat is

 fs/ext2/ext2.h        |  3 ++-
 fs/ext2/super.c       |  7 +++++++
 fs/ext2/xattr.c       |  1 -
 fs/quota/Kconfig      |  4 ++--
 fs/quota/dquot.c      | 24 ++----------------------
 fs/quota/quota_v1.c   |  2 +-
 fs/quota/quota_v2.c   |  2 +-
 fs/reiserfs/journal.c |  2 --
 fs/reiserfs/stree.c   |  2 --
 fs/udf/inode.c        | 10 +++++-----
 fs/udf/truncate.c     |  4 ++--
 11 files changed, 22 insertions(+), 39 deletions(-)

							Thanks
								Honza

-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

             reply	other threads:[~2023-04-25 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 10:35 Jan Kara [this message]
2023-04-26 17:06 ` [GIT PULL] ext2, reiserfs, udf, and quota cleanups and fixes for 6.4-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=20230425103501.ib4qoy4j5a3mzf2c@quack3 \
    --to=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@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