All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Patchwork summary for: f2fs
Date: Thu, 06 Jul 2023 00:18:14 +0000	[thread overview]
Message-ID: <168860269448.29151.7314555898251097801.git-patchwork-summary@kernel.org> (raw)

Hello:

The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):

Series: [f2fs-dev,01/12] backing_dev: remove current->backing_dev_info
  Submitter: Christoph Hellwig <hch@lst.de>
  Committer: Andrew Morton <akpm@linux-foundation.org>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=753162
  Lore link: https://lore.kernel.org/r/20230601145904.1385409-2-hch@lst.de
    Patches: [f2fs-dev,01/12] backing_dev: remove current->backing_dev_info
             [f2fs-dev,02/12] iomap: update ki_pos a little later in iomap_dio_complete
             [f2fs-dev,03/12] filemap: update ki_pos in generic_perform_write
             [f2fs-dev,04/12] filemap: add a kiocb_write_and_wait helper
             [f2fs-dev,05/12] filemap: add a kiocb_invalidate_pages helper
             [f2fs-dev,06/12] filemap: add a kiocb_invalidate_post_direct_write helper
             [f2fs-dev,07/12] iomap: update ki_pos in iomap_file_buffered_write
             [f2fs-dev,08/12] iomap: use kiocb_write_and_wait and kiocb_invalidate_pages
             [f2fs-dev,09/12] fs: factor out a direct_write_fallback helper
             [f2fs-dev,10/12] fuse: update ki_pos in fuse_perform_write
             [f2fs-dev,11/12] fuse: drop redundant arguments to fuse_perform_write
             [f2fs-dev,12/12] fuse: use direct_write_fallback

Series: [f2fs-dev,01/30] block: also call ->open for incremental partition opens
  Submitter: Christoph Hellwig <hch@lst.de>
  Committer: Jens Axboe <axboe@kernel.dk>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=755281
  Lore link: https://lore.kernel.org/r/20230608110258.189493-2-hch@lst.de
    Patches: [f2fs-dev,01/30] block: also call ->open for incremental partition opens
             [f2fs-dev,02/30] cdrom: remove the unused bdev argument to cdrom_open
             [f2fs-dev,03/30] cdrom: remove the unused mode argument to cdrom_ioctl
             [f2fs-dev,04/30] cdrom: remove the unused cdrom_close_write release code
             [f2fs-dev,05/30] cdrom: track if a cdrom_device_info was opened for data
             [f2fs-dev,06/30] cdrom: remove the unused mode argument to cdrom_release
             [f2fs-dev,07/30] block: pass a gendisk on bdev_check_media_change
             [f2fs-dev,08/30] block: pass a gendisk to ->open
             [f2fs-dev,09/30] block: remove the unused mode argument to ->release
             [f2fs-dev,10/30] block: rename blkdev_close to blkdev_release
             [f2fs-dev,11/30] swsusp: don't pass a stack address to blkdev_get_by_path
             [f2fs-dev,12/30] bcache: don't pass a stack address to blkdev_get_by_path
             [f2fs-dev,13/30] rnbd-srv: don't pass a holder for non-exclusive blkdev_get_by_path
             [f2fs-dev,14/30] btrfs: don't pass a holder for non-exclusive blkdev_get_by_path
             [f2fs-dev,15/30] block: use the holder as indication for exclusive opens
             [f2fs-dev,16/30] block: add a sb_open_mode helper
             [f2fs-dev,17/30] fs: remove sb->s_mode
             [f2fs-dev,18/30] scsi: replace the fmode_t argument to scsi_cmd_allowed with a simple bool
             [f2fs-dev,19/30] scsi: replace the fmode_t argument to scsi_ioctl with a simple bool
             [f2fs-dev,20/30] scsi: replace the fmode_t argument to ->sg_io_fn with a simple bool
             [f2fs-dev,21/30] nvme: replace the fmode_t argument to the nvme ioctl handlers with a simple bool
             [f2fs-dev,22/30] mtd: block: use a simple bool to track open for write
             [f2fs-dev,23/30] rnbd-srv: replace sess->open_flags with a "bool readonly"
             [f2fs-dev,24/30] ubd: remove commented out code in ubd_open
             [f2fs-dev,25/30] block: move a few internal definitions out of blkdev.h
             [f2fs-dev,26/30] block: remove unused fmode_t arguments from ioctl handlers
             [f2fs-dev,27/30] block: replace fmode_t with a block-specific type for block open flags
             [f2fs-dev,28/30] block: always use I_BDEV on file->f_mapping->host to find the bdev
             [f2fs-dev,29/30] block: store the holder in file->private_data
             [f2fs-dev,30/30] fs: remove the now unused FMODE_* flags

Series: [f2fs-dev,01/17] fs: unexport buffer_check_dirty_writeback
  Submitter: Christoph Hellwig <hch@lst.de>
  Committer: Christian Brauner <brauner@kernel.org>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=742589
  Lore link: https://lore.kernel.org/r/20230424054926.26927-2-hch@lst.de
    Patches: [f2fs-dev,01/17] fs: unexport buffer_check_dirty_writeback
             [f2fs-dev,02/17] fs: remove the special !CONFIG_BLOCK def_blk_fops
             [f2fs-dev,06/17] filemap: add a kiocb_write_and_wait helper
             [f2fs-dev,07/17] filemap: add a kiocb_invalidate_pages helper
             [f2fs-dev,13/17] block: don't plug in blkdev_write_iter

Series: [f2fs-dev,01/13] iomap: update ki_pos a little later in iomap_dio_complete
  Submitter: Christoph Hellwig <hch@lst.de>
  Committer: Andrew Morton <akpm@linux-foundation.org>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=749185
  Lore link: https://lore.kernel.org/r/20230519093521.133226-2-hch@lst.de
    Patches: [f2fs-dev,01/13] iomap: update ki_pos a little later in iomap_dio_complete
             [f2fs-dev,04/13] filemap: add a kiocb_write_and_wait helper
             [f2fs-dev,05/13] filemap: add a kiocb_invalidate_pages helper
             [f2fs-dev,09/13] iomap: use kiocb_write_and_wait and kiocb_invalidate_pages

Patch: None
  Submitter: David Howells <dhowells@redhat.com>
  Committer: Jens Axboe <axboe@kernel.dk>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=749500
  Lore link: https://lore.kernel.org/r/20230520000049.2226926-20-dhowells@redhat.com

Patch: None
  Submitter: David Howells <dhowells@redhat.com>
  Committer: Jens Axboe <axboe@kernel.dk>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=749786
  Lore link: https://lore.kernel.org/r/20230522135018.2742245-20-dhowells@redhat.com

Patch: [f2fs-dev,v2] fsverity: use shash API instead of ahash API
  Submitter: Eric Biggers <ebiggers@kernel.org>
  Committer: Eric Biggers <ebiggers@google.com>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=747847
  Lore link: https://lore.kernel.org/r/20230516052306.99600-1-ebiggers@kernel.org

Series: fs: Fix directory corruption when moving directories
  Submitter: Jan Kara <jack@suse.cz>
  Committer: Christian Brauner <brauner@kernel.org>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=753052
  Lore link: https://lore.kernel.org/r/20230601104525.27897-1-jack@suse.cz
    Patches: [f2fs-dev,v2,1/6] ext4: Remove ext4 locking of moved directory
             [f2fs-dev,v2,2/6] Revert "udf: Protect rename against modification of moved directory"
             [f2fs-dev,v2,3/6] Revert "f2fs: fix potential corruption when moving a directory"
             [f2fs-dev,v2,5/6] fs: Lock moved directories

Patch: [f2fs-dev,GIT,PULL] f2fs update for 6.5
  Submitter: Jaegeuk Kim <jaegeuk@kernel.org>
  Committer: Linus Torvalds <torvalds@linux-foundation.org>
  Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=762798
  Lore link: https://lore.kernel.org/r/ZKWuP6+mGdW/W0/P@google.com


Total patches: 59

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

             reply	other threads:[~2023-07-06  0:18 UTC|newest]

Thread overview: 161+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  0:18 patchwork-bot+f2fs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-14 23:30 [f2fs-dev] Patchwork summary for: f2fs patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-11  1:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-11  1:41 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-01  4:52 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-18 22:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-15 16:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-13 23:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-02 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-03-24 17:32 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-03-05 19:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-02-17 21:14 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-02-10 21:28 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-30 17:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-27  2:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-22 23:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-19 13:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-16  3:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-07  3:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-16 19:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-16  0:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-09 17:18 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-03 21:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-02 18:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-11-24 18:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-11-11 22:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-16 18:24 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-10 16:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-06 18:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-06 17:38 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-02 20:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-09-29 22:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-09-02 20:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-08-15 16:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-30 17:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-28 16:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-24 20:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-18 20:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-11 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-11 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-09 18:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-24  0:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-18 21:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-09 20:56 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-28 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-14 15:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-08 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-06 15:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-30  2:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-28 22:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-14 22:57 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-12 17:11 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-10  4:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-27 21:58 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-18  1:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-14 22:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-13 18:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-12 15:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-11 19:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-11  3:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-05 14:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-04 17:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-01  1:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-28 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-21  2:17 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-12  3:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-12  2:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-10 17:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-10 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-06 18:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-29  0:56 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-25  1:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-22 21:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-21 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-17 21:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-13 18:51 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-08 18:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-12-16 16:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-23 15:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-21 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-18 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-07 20:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-28 17:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-14 20:11 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-10 20:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-09-25  3:41 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-09-16 21:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-08-30 20:51 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-08-05 23:30 patchwork-bot+f2fs
2024-07-24  2:16 patchwork-bot+f2fs
2024-07-15 14:40 patchwork-bot+f2fs
2024-07-03 15:20 patchwork-bot+f2fs
2024-06-24 17:40 patchwork-bot+f2fs
2024-06-12 15:55 patchwork-bot+f2fs
2024-05-20 21:16 patchwork-bot+f2fs
2024-05-15  4:20 patchwork-bot+f2fs
2024-05-11  0:50 patchwork-bot+f2fs
2024-04-25 15:40 patchwork-bot+f2fs
2024-04-24 17:40 patchwork-bot+f2fs
2024-04-23 17:40 patchwork-bot+f2fs
2024-04-14 15:32 patchwork-bot+f2fs
2024-03-18 20:45 patchwork-bot+f2fs
2024-03-14 16:20 patchwork-bot+f2fs
2024-03-13  1:30 patchwork-bot+f2fs
2024-03-06 17:50 patchwork-bot+f2fs
2024-03-04 18:20 patchwork-bot+f2fs
2024-02-28 22:50 patchwork-bot+f2fs
2024-02-21 18:10 patchwork-bot+f2fs
2024-01-30 20:50 patchwork-bot+f2fs
2024-01-29 20:29 patchwork-bot+f2fs
2024-01-16 19:02 patchwork-bot+f2fs
2023-12-29 19:10 patchwork-bot+f2fs
2023-12-14 20:50 patchwork-bot+f2fs
2023-11-30 18:30 patchwork-bot+f2fs
2023-10-23 15:30 patchwork-bot+f2fs
2023-09-20 15:50 patchwork-bot+f2fs
2023-09-04 18:11 patchwork-bot+f2fs
2023-08-28 17:20 patchwork-bot+f2fs
2023-08-25 17:30 patchwork-bot+f2fs
2023-08-21 19:50 patchwork-bot+f2fs
2023-08-14 20:50 patchwork-bot+f2fs
2023-08-07 20:00 patchwork-bot+f2fs
2023-07-17 17:34 patchwork-bot+f2fs
2023-06-30 23:40 patchwork-bot+f2fs
2023-06-26 13:30 patchwork-bot+f2fs
2023-06-22  7:11 patchwork-bot+f2fs
2023-06-16 23:50 patchwork-bot+f2fs
2023-06-15 18:00 patchwork-bot+f2fs
2023-06-12 20:50 patchwork-bot+f2fs
2023-06-07 17:30 patchwork-bot+f2fs
2023-05-30 23:40 patchwork-bot+f2fs
2023-05-18  1:50 patchwork-bot+f2fs
2023-05-08 18:34 patchwork-bot+f2fs
2023-04-26 23:07 patchwork-bot+f2fs
2023-04-24 18:10 patchwork-bot+f2fs
2023-04-17 21:50 patchwork-bot+f2fs
2023-04-13 23:40 patchwork-bot+f2fs
2023-04-12 16:20 patchwork-bot+f2fs
2023-04-11 17:00 patchwork-bot+f2fs
2023-04-05 16:20 patchwork-bot+f2fs
2023-04-04 21:30 patchwork-bot+f2fs
2023-04-04  1:54 patchwork-bot+f2fs
2023-04-03 18:30 patchwork-bot+f2fs
2023-03-29 22:21 patchwork-bot+f2fs
2023-03-27 16:00 patchwork-bot+f2fs
2023-03-21 16:40 patchwork-bot+f2fs
2023-03-13 20:20 patchwork-bot+f2fs
2023-03-07 17:40 patchwork-bot+f2fs
2023-02-28  1:01 patchwork-bot+f2fs
2023-02-15 18:00 patchwork-bot+f2fs
2023-02-14 18:10 patchwork-bot+f2fs
2023-02-10 21:40 patchwork-bot+f2fs
2023-02-07 19:00 patchwork-bot+f2fs
2023-02-06  3:50 patchwork-bot+f2fs
2023-02-06  3:40 patchwork-bot+f2fs
2023-01-31 19:10 patchwork-bot+f2fs
2023-01-30 23:00 patchwork-bot+f2fs
2023-01-11 19:20 patchwork-bot+f2fs
2023-01-09 22:51 patchwork-bot+f2fs
2023-01-03 18:50 patchwork-bot+f2fs
2023-01-03 17:03 patchwork-bot+f2fs

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=168860269448.29151.7314555898251097801.git-patchwork-summary@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.