All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: [GIT PULL] File system related bio_alloc() cleanups
Date: Fri, 18 Mar 2022 15:59:34 -0600	[thread overview]
Message-ID: <212e39c2-2e2a-24af-647b-67f3168ea558@kernel.dk> (raw)

Hi Linus,

On top of the core block driver branch, here are a set of fs related
cleanups to bio allocations.

Please pull!


The following changes since commit 451f0b6f4c44d7b649ae609157b114b71f6d7875:

  block: default BLOCK_LEGACY_AUTOLOAD to y (2022-02-27 14:49:23 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/for-5.18/alloc-cleanups-2022-03-18

for you to fetch changes up to 64bf0eef0171912f7c2f3ea30ee6ad7a2ad0a511:

  f2fs: pass the bio operation to bio_alloc_bioset (2022-03-08 17:59:03 -0700)

----------------------------------------------------------------
for-5.18/alloc-cleanups-2022-03-18

----------------------------------------------------------------
Christoph Hellwig (5):
      mpage: pass the operation to bio_alloc
      ext4: pass the operation to bio_alloc
      nilfs2: pass the operation to bio_alloc
      f2fs: don't pass a bio to f2fs_target_device
      f2fs: pass the bio operation to bio_alloc_bioset

 fs/ext4/page-io.c  |  7 ++---
 fs/f2fs/data.c     | 89 ++++++++++++++++++++++++------------------------------
 fs/f2fs/f2fs.h     |  2 +-
 fs/mpage.c         | 50 +++++++++++++-----------------
 fs/nilfs2/segbuf.c | 20 ++++++------
 5 files changed, 73 insertions(+), 95 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2022-03-18 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 21:59 Jens Axboe [this message]
2022-03-22  0:25 ` [GIT PULL] File system related bio_alloc() cleanups 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=212e39c2-2e2a-24af-647b-67f3168ea558@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@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 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.